Not for raw I/O. Although for the drivers that can't cope then going via
the page cache is certainly the next best alternative
> The real thing is that we want to have some common data structure for
> describing physical memory used for IO. We could either use special
Yes. You also need a way to describe it in terms of page * in order to do
mm locking for raw I/O (like the video capture stuff wants)
> by Larry McVoy's splice paper) should allow just that, nothing more an
> nothing less. For use in disk-io and networking or v4l there are probably
> other primary data structures needed, and that's ok.
Certainly having the lightweight one a subset of the heavyweight one is a good
target.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/