Re: [patch 2/5] fs: introduce new aops and infrastructure

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Dmitriy Monakhov
Date: Thursday, March 15, 2007 - 2:44 am

Nick Piggin <npiggin@suse.de> writes:

One more note. It's looks like you just disabled all fancy zero copy logic.
Off corse this is just rfc patchset.
But i think where is fundamental problem with it:
 Previous logic was following:
  1)splice code responsible for: stealing(if possible) and loking the page
  2)prepare_write() code responsible for: do fs speciffic stuff

 But with new write_begin() logic  all steps (grubbing, locking, preparing)
 happened internaly inside write_begin() witch doesn't even know about what
 kind of data will be copied between write_begin/write_end.
 So fancy zero copy logic is impossible :(
I think this can be solved somehow, but i dont know yet, how can this be done
without implementing it inside begin_write().


-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[patch 1/5] fs: add an iovec iterator, Nick Piggin, (Wed Mar 14, 6:38 am)
[patch 2/5] fs: introduce new aops and infrastructure, Nick Piggin, (Wed Mar 14, 6:38 am)
[patch 3/5] fs: convert some simple filesystems, Nick Piggin, (Wed Mar 14, 6:38 am)
[patch 4/5] ext2: convert to new aops, Nick Piggin, (Wed Mar 14, 6:38 am)
[patch 5/5] ext3: convert to new aops, Nick Piggin, (Wed Mar 14, 6:38 am)
Re: [patch 1/5] fs: add an iovec iterator, Nick Piggin, (Wed Mar 14, 6:51 am)
Re: [patch 2/5] fs: introduce new aops and infrastructure, Dmitriy Monakhov, (Wed Mar 14, 2:28 pm)
Re: [patch 2/5] fs: introduce new aops and infrastructure, Dmitriy Monakhov, (Thu Mar 15, 2:44 am)
Re: [patch 2/5] fs: introduce new aops and infrastructure, Steven Whitehouse, (Thu Mar 15, 9:24 am)
Re: [patch 2/5] fs: introduce new aops and infrastructure, Trond Myklebust, (Thu Mar 15, 1:06 pm)