On Thu, Nov 07, 2013 at 11:39:59PM -0800, Kent Overstreet wrote: > On Thu, Nov 07, 2013 at 11:33:24PM -0800, Christoph Hellwig wrote: > > The changes for direct I/O from kernel space have been in for a long > > time, and they are blocking multiple consumers of the interface from > > getting submitted for about a year now. Even if the guts of the > > direct-io code will get a write based on another patchset from Kent > > that will go on top of the immutable iovec changes we need the > > interfaces now and not another year down the road. > > What else is blocked on this patch series? Honest question. >From me alone: Support for ecryptfs to not double cache. AIO support for target_core_file. To replace code in staging: Removal of the lustre-specific loop driver. And I remember others claiming to want to submit bits, too. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
