On Tue, Aug 23, 2005 at 05:56:09AM -0400, Jakub Jelinek wrote:
> 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
Le mar 23/08/2005 à 11:56, Jakub Jelinek a écrit :
> 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
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
>
Ingo suggested putting together a summary note describing the status (e.g.
pending out-of-tree patches) and TODO items that need fixing in the mainline
linux kernel AIO implementation to get good AIO support in both kernel-space
and user-space, starting with enabling reasonably efficient and
Ingo suggested putting together a summary note describing the status (e.g.
pending out-of-tree patches) and TODO items that need fixing in the mainline
linux kernel AIO implementation to get good AIO support in both kernel-space
and user-space, starting with enabling reasonably efficient and
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
Le mar 23/08/2005 à 11:56, Jakub Jelinek a écrit :
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
On Tue, Aug 23, 2005 at 05:56:09AM -0400, Jakub Jelinek wrote:
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
8 matches
Mail list logo
