[lkml]   [2001]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: About I/O callbacks ...

On 22-Jun-2001 Andi Kleen wrote:
> Davide Libenzi <> writes:
>> I was just thinking to implement I/O callbacks inside the kernel and test
>> which
>> kind of performance could result compared to a select()/poll()
>> implementation.
>> I prefer IO callbacks against async-io coz in this way is more direct to
>> implement an I/O driven state machine + coroutines.
>> This is a first draft :
> They already exist since several years in Linux.
> It is called queued SIGIO; when you set a realtime signal
> using F_SETSIG for a fd and enable async IO. The callback is a signal
> handler or alternatively an event processing loop using sigwaitinfo*().
> The necessary information like which fd got an event is passed in the
> siginfo_t.

I know about rt signals and SIGIO :) but I can't see how You can queue signals :


The action field is an array so if more than one I/O notification is fired
before the SIGIO is delivered, You'll deliver only the last one.
Am I missing something ?

- Davide

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:17    [W:0.037 / U:0.284 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site