Rich man's version of AIO on Linux 2.6.x?
Hello,
On the state-of-art of asynchronous I/O in Linux. I understand we have full support for AIO in the Linux 2.6.x kernel but I cannot find how to use it from user space.
I would like to exploit AIO in hardware and the device driver for it, by keeping the hardware performing I/O at all times (no setup latency between requests by allowing multiple
I/O requests to be queued in hardware). Note this is a character device, not a filesystem.
I implemented aio_read() and aio_write() on my character device interface, but it's never been called; read() and write() is called instead.
Quoted 1 line
From "Understanding the Linux kernel, 3rd edition" I read that glibc
indeed implements aio_read() and friends itself, not through the kernel AIO syscalls.
<Quote>
Essentially, the aio_read( ) or aio_write( ) library function clones the current process and lets the child invoke the synchronous read( ) or write( ) system calls; However, this "poor man's" version of the POSIX functions is significantly slower than a version that uses a kernel-level implementation of asynchronous I/O.
<End Quote>
I am looking for a rich man's way to use the kernel functionality; essentially I want my drivers aio_read and aio_write ops to be called.
Regards,
Signature · 1 line
Leon
Quoted 1 line · Leon Woestenberg
Hello,
Hi
Quoted 28 lines
On the state-of-art of asynchronous I/O in Linux. I understand we have full support for AIO in the Linux 2.6.x kernel but I cannot find how to use it from user space.
I would like to exploit AIO in hardware and the device driver for it, by keeping the hardware performing I/O at all times (no setup latency between requests by allowing multiple
I/O requests to be queued in hardware). Note this is a character device, not a filesystem.I implemented
aio_read()andaio_write()on my character device interface, but it's never been called;read()andwrite()is called instead.From "Understanding the Linux kernel, 3rd edition" I read that glibc indeed implements
aio_read()and friends itself, not through the kernel AIO syscalls.<Quote>
Essentially, theaio_read( )oraio_write( )library function clones the current process and lets the child invoke the synchronousread( )orwrite( )system calls; However, this "poor man's" version of the POSIX functions is significantly slower than a version that uses a kernel-level implementation of asynchronous I/O.
<End Quote>
Quoted 2 lines
I am looking for a rich man's way to use the kernel functionality; essentially I want my drivers
aio_readandaio_writeops to be called.
Check the libaio library (io_submit and friends)
Quoted 9 lines
Regards,
Signature · 6 lines
Leon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Signature · 6 lines
Michal Hocko L3 team SUSE LINUX s.r.o. Lihovarska 1060/12 190 00 Praha 9 Czech Republic
Hello,
Quoted 5 lines · Michal Hocko
Quoted 4 lines · Leon Woestenberg
On the state-of-art of asynchronous I/O in Linux. I understand we have full support for AIO in the Linux 2.6.x kernel but I cannot find how to use it from user space.
Quoted 8 lines
Quoted 5 lines
I would like to exploit AIO in hardware and the device driver for it, by keeping the hardware performing I/O at all times (no setup latency between requests by allowing multiple
I/O requests to be queued in hardware). Note this is a character device, not a filesystem.Check the libaio library (
io_submitand friends)
Thanks, I checked the libaio library. It does not support the POSIX interface, which I'ld like to use to keep things portable.
The http://www.bullopensource.org/posix/ library is more promising in that regard but it doesn't seem maintained.
Regards,
Signature · 1 line
Leon