lkml.org 
[lkml]   [2000]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Changes in the sockets: SIGIO handling
Hi,

On Tue, 7 Mar 2000 21:11:04 +0300 (MSK), kuznet@ms2.inr.ac.ru said:

>> IMO a callback device that you simply read() the siginfo from would be
>> much the cleaner API.

> Well, batched signal delivery is apparently required feature,
> when signals are queued. There are no questions here.

What's the problem? The expected mode of operation here is that the
caller will always have the signal blocked and will use sigtimedwait()
to dequeue siginfo structures synchronously in place of calling
poll().

> But do not forget that even generation of such signals is not a zero
> overhead, which can be saved as rule. F.e. both old and rt signals
> are not generated at all when someone _sleeps_ in read()/write().

Are you sure? Even if the signal is blocked?

--Stephen

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

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