Re: block device direct I/O fast path

2016-11-01 Thread Jens Axboe
On 11/01/2016 11:54 AM, Jens Axboe wrote: On Tue, Nov 01 2016, Christoph Hellwig wrote: On Tue, Nov 01, 2016 at 11:00:19AM -0600, Jens Axboe wrote: #2 is a bit more problematic, I'm pondering how we can implement that on top of the bio approach. The nice thing about the request based approach i

Re: block device direct I/O fast path

2016-11-01 Thread Jens Axboe
On Tue, Nov 01 2016, Christoph Hellwig wrote: > On Tue, Nov 01, 2016 at 11:00:19AM -0600, Jens Axboe wrote: > > #2 is a bit more problematic, I'm pondering how we can implement that on > > top of the bio approach. The nice thing about the request based approach > > is that we have a 1:1 mapping wit

Re: block device direct I/O fast path

2016-11-01 Thread Christoph Hellwig
On Tue, Nov 01, 2016 at 11:00:19AM -0600, Jens Axboe wrote: > #2 is a bit more problematic, I'm pondering how we can implement that on > top of the bio approach. The nice thing about the request based approach > is that we have a 1:1 mapping with the unit on the driver side. And we > have a place t

Re: block device direct I/O fast path

2016-11-01 Thread Jens Axboe
On Mon, Oct 31 2016, Christoph Hellwig wrote: > Hi Jens, > > this small series adds a fasth path to the block device direct I/O > code. It uses new magic created by Kent to avoid allocating an array > for the pages, and as part of that allows small, non-aio direct I/O > requests to be done withou

block device direct I/O fast path

2016-10-31 Thread Christoph Hellwig
Hi Jens, this small series adds a fasth path to the block device direct I/O code. It uses new magic created by Kent to avoid allocating an array for the pages, and as part of that allows small, non-aio direct I/O requests to be done without memory allocations or atomic ops and with a minimal cach