Re: [PATCH 27/27] aio: add support for pre-mapped user IO buffers

2018-11-30 Thread Jens Axboe
On 11/30/18 3:04 PM, Jeff Moyer wrote: > Jens Axboe writes: > A limit of 4M is imposed as the largest buffer we currently support. There's nothing preventing us from going larger, but we need some cap, and 4M seemed like it would definitely be big enough. >>> >>> Doesn't this mean

Re: [PATCH 27/27] aio: add support for pre-mapped user IO buffers

2018-11-30 Thread Jeff Moyer
Jens Axboe writes: >>> A limit of 4M is imposed as the largest buffer we currently support. >>> There's nothing preventing us from going larger, but we need some cap, >>> and 4M seemed like it would definitely be big enough. >> >> Doesn't this mean that a user can pin a bunch of memory?

Re: [PATCH 27/27] aio: add support for pre-mapped user IO buffers

2018-11-30 Thread Jens Axboe
On 11/30/18 2:44 PM, Jeff Moyer wrote: > Hi, Jens, > > Jens Axboe writes: > >> If we have fixed user buffers, we can map them into the kernel when we >> setup the io_context. That avoids the need to do get_user_pages() for >> each and every IO. >> >> To utilize this feature, the application

Re: [PATCH 27/27] aio: add support for pre-mapped user IO buffers

2018-11-30 Thread Jeff Moyer
Hi, Jens, Jens Axboe writes: > If we have fixed user buffers, we can map them into the kernel when we > setup the io_context. That avoids the need to do get_user_pages() for > each and every IO. > > To utilize this feature, the application must set both > IOCTX_FLAG_USERIOCB, to provide iocb's

[PATCH 27/27] aio: add support for pre-mapped user IO buffers

2018-11-30 Thread Jens Axboe
If we have fixed user buffers, we can map them into the kernel when we setup the io_context. That avoids the need to do get_user_pages() for each and every IO. To utilize this feature, the application must set both IOCTX_FLAG_USERIOCB, to provide iocb's in userspace, and then