Linus,
We talked before about a general purpose kernel IO buffer mechanism that
can be used to pass arbitrary data around for IO, and how that could
hide the mess of zero-copy raw user IO from the kernel IO layers. I
have a working implementation, although I'm still soliciting input as to
what t
Hi Linus,
I have a patch I've been trying out to improve fsync performance by
maintaining per-inode dirty buffer lists, and to implement fdatasync by
tracking "significant" and "insignificant" (ie. timestamp) dirty flags
in the inode separately. However, in doing this I found a serious
problem
