Re: [RFC] fs io with struct page instead of iovecs

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Zach Brown
Date: Wednesday, November 7, 2007 - 10:02 am

Badari Pulavarty wrote:

Well, I think there's a few:

There are existing callers which hold a kmap() across ->write, which
isn't great.  ecryptfs() does this.  That's mentioned in the patch
series.  Arguably loopback should be using this instead of copying some
fs paths and trying to call aop methods directly.

I seem to remember Christoph and David having stories of knfsd folks in
SGI wanting to do O_DIRECT writes from knfsd?  (If not, *I* kind of want
to, after rolling some patches to align net rx descriptors :)).

Lustre shows us that there is a point at which you can't saturate your
network and storage if your cpu is copying all the data.  I'll be the
first to admit that the community might not feel a pressing need to
address this for in-kernel file system writers, but the observation remains.

- z
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[RFC] fs io with struct page instead of iovecs, Zach Brown, (Tue Nov 6, 6:43 pm)
[PATCH 3/4] add rwmem type backed by pages, Zach Brown, (Tue Nov 6, 6:43 pm)
Re: [RFC] fs io with struct page instead of iovecs, Badari Pulavarty, (Wed Nov 7, 9:50 am)
Re: [RFC] fs io with struct page instead of iovecs, Zach Brown, (Wed Nov 7, 10:02 am)
Re: [RFC] fs io with struct page instead of iovecs, David Chinner, (Wed Nov 7, 1:44 pm)