aio: make use of ring code optional
authorJens Axboe <axboe@kernel.dk>
Sun, 21 Apr 2013 04:26:14 +0000 (21:26 -0700)
committerJens Axboe <axboe@kernel.dk>
Mon, 22 Apr 2013 01:29:58 +0000 (19:29 -0600)
commit9bde77284ad2d342c63c84599fa8c11a086f02b9
tree92677e540d8ed74554416f75745bfcb1a0fc4685
parent34a3abbfd0cfea45dc090a70cc521de31fc2a8f5
aio: make use of ring code optional

Make use of the ring optional. Nobody uses the aio user mappable ring,
yet we center our completion/submission interface around it. Allow a
user to pass in INT_MAX to io_queue_init() to signal that he doesn't
care about the ring, since he uses the regular getevents() to retrieve
events. I'd like to use 0 since that more elegantly mirrors size of
the ring, but that magic value is caught and rejected by the libaio
wrapper around io_queue_init()...

Signed-off-by: Jens Axboe <axboe@kernel.dk>
fs/aio.c
include/linux/aio.h