From: Davide Libenzi <davidel@xmailserver.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: About I/O callbacks ...
Date: Fri, 22 Jun 2001 09:07:08 -0700 (PDT) [thread overview]
Message-ID: <XFMail.20010622090708.davidel@xmailserver.org> (raw)
In-Reply-To: <20010622175944.A6968@gruyere.muc.suse.de>
On 22-Jun-2001 Andi Kleen wrote:
> On Fri, Jun 22, 2001 at 08:55:00AM -0700, Davide Libenzi wrote:
>> I know about rt signals and SIGIO :) but I can't see how You can queue
>> signals :
>>
>> current->sig->action[..]
>>
>> 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 ?
>
> Yes. Realtime signals (>=SIGRTMIN) get queued in current->pending.
Damn right.
- Davide
next prev parent reply other threads:[~2001-06-22 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <XFMail.20010621184645.davidel@xmailserver.org.suse.lists.linux.kernel>
2001-06-22 7:49 ` About I/O callbacks Andi Kleen
2001-06-22 15:55 ` Davide Libenzi
2001-06-22 15:59 ` Andi Kleen
2001-06-22 16:07 ` Davide Libenzi [this message]
2001-06-22 22:23 ` Davide Libenzi
2001-06-22 1:46 Davide Libenzi
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=XFMail.20010622090708.davidel@xmailserver.org \
--to=davidel@xmailserver.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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