From: Jakub Jelinek <jakub@redhat.com>
To: Suparna Bhattacharya <suparna@in.ibm.com>
Cc: Ulrich Drepper <drepper@redhat.com>, Ingo Molnar <mingo@elte.hu>,
akpm@osdl.org, linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Linux AIO status & todo
Date: Tue, 23 Aug 2005 05:56:09 -0400 [thread overview]
Message-ID: <20050823095609.GZ7403@devserv.devel.redhat.com> (raw)
In-Reply-To: <20050823074438.GA4586@in.ibm.com>
On Tue, Aug 23, 2005 at 01:14:38PM +0530, Suparna Bhattacharya wrote:
> 2. No support for propagating IO completion events to user space
> threads using RT signals. User threads need to poll the completion
> queue using io_getevents. POSIX specifies that when an AIO
> request completes, a signal can be delivered to the application
> to indicate the completion of the IO.
POSIX AIO needs to handle SIGEV_NONE, SIGEV_SIGNAL and SIGEV_THREAD
notification. Obviously kernel shouldn't create threads for SIGEV_THREAD
itself, as kernel shouldn't hardcode all the implementation details how a
thread can be created. But it would be good if AIO signalling e.g. handled
both SIGEV_SIGNAL and SIGEV_SIGNAL | SIGEV_THREAD_ID, with the same usage as
e.g. timer_* syscalls. If kernel makes sure SI_ASYNCIO si_code is set in
the notification signal siginfos, glibc could even use just one helper
thread for timer_*/[al]io_* and maybe in the future other SIGEV_THREAD notification.
Jakub
next prev parent reply other threads:[~2005-08-23 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 7:44 Linux AIO status & todo Suparna Bhattacharya
2005-08-23 9:56 ` Jakub Jelinek [this message]
2005-08-23 13:13 ` Laurent Vivier
2005-08-23 16:57 ` Benjamin LaHaise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050823095609.GZ7403@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suparna@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox