On Tue, Feb 04, 2014 at 12:44:09PM +0000, Al Viro wrote: > On Mon, Feb 03, 2014 at 10:23:13AM -0600, Dave Kleikamp wrote: > > > Thanks for the feedback. I'd been asking for feedback on this patchset > > for some time now, and have not received very much. > > > > This is all based on some years-old work by Zach Brown that he probably > > wishes would have disappeared by now. I pretty much left what I could > > alone since 1) it was working, and 2) I didn't hear any objections > > (until now). > > > > It's clear now that the patchset isn't close to mergable, so treat it > > like a proof-of-concept and we can come up with a better container and > > read/write interface. I won't respond individually to your comments, but > > will take them all into consideration going forward. > > FWIW, I suspect that the right way to deal with dio side of things would > be a primitive along the lines of "get first N <page,start,len> for the > iov_iter". With get_user_pages_fast() for iovec-backed ones and "just > grab references" for array-of-page-subranges ones. I'm on vacation in Switzerland, didn't bring my adderall, and direct-io.c makes my head hurt at the best of times, but - have a look at my in-progress dio rewrite: http://evilpiepirate.org/git/linux-bcache.git/commit/?h=block_stuff&id=ca09c20f08efd640f255fabd778de0dbf43ed1da Where I'm headed with things is to just start out by allocating bios and pinning pages into them, and _then_ doing all the fun "ask the filesystem where it goes and what to do with it" dance. The goal is to push the bios as far up the stack as possible. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
