This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug librt/20950] Do asynchronous execution for lio_listio's IOs
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 26 Jan 2017 10:48:53 +0000
- Subject: [Bug librt/20950] Do asynchronous execution for lio_listio's IOs
- Auto-submitted: auto-generated
- References: <bug-20950-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20950
--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Ulrich Windl from comment #2)
> (In reply to Florian Weimer from comment #1)
> > Out of curiosity, is there a reason why you cannot use libaio instead of the
> > glibc aio interface? Thanks.
>
> Two reasons:
> 1) It (lio_listio()) is POSIX, so it may run on several machines.
> 2) I didn't know that there are two implementations ;-)
Ah. I was asking because it is not likely that we will make further changes to
the thread-based aio implementation in glibc.
I'm not sure if Linux actually offers truly asynchronous buffered I/O. Some
thread is needed to drive the I/O. But glibc (or any other aio implementation)
cannot spawn a separate thread for each I/O operation in the list because that
could lead to I/O thrashing.
I'm sorry but I think we should close this bug as WONTFIX.
--
You are receiving this mail because:
You are on the CC list for the bug.