mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch 1/4] signalfd v1 - signalfd core ...
Date: Wed, 7 Mar 2007 09:50:10 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703070943180.12283@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703070854280.5963@woody.linux-foundation.org>

On Wed, 7 Mar 2007, Linus Torvalds wrote:

> On Wed, 7 Mar 2007, Stephen Rothwell wrote:
> > 
> > You probably need the queue anyway because the real time signals are
> > supposed to queue.
> 
> Davide - the *real* problem is (I think) that you try to allow signals to 
> be returned *both* by signalfd() and as a real signal.
> 
> That's wrong, wrong, wrong.
> 
> My original patch used "dequeue_signal()" to dequeue signals. Trust me, I 
> did that for a reason. Your re-design to think that you can get the signal 
> without using the real signal dequeueing is simply broken.

I think having the ability to have both can be usefull, so the idea of 
having multiple listeners fd (that both would not work with the single 
queue since they'd racing over dequeue_signal).
The two place where I plugges signalfd_notify() has the siginfo already 
compiled, so I just need to:

1) Pass the siginfo pointer to signalfd_notify too

2) Switch from having a bitmap, to a struct list_head queue

3) Dequeue and return the signal and siginfo inside a compat-free 
   structure

The #2 makes code even easier actually. The poll would just do a 
list_empty(), and dequeueing is just get-head and list_del().



- Davide



  reply	other threads:[~2007-03-07 17:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07  1:36 Davide Libenzi
2007-03-07  1:43 ` Davide Libenzi
2007-03-07  4:55 ` Stephen Rothwell
2007-03-07  7:11   ` Davide Libenzi
2007-03-07 12:38     ` Stephen Rothwell
2007-03-07 16:57       ` Linus Torvalds
2007-03-07 17:50         ` Davide Libenzi [this message]
2007-03-07 20:30           ` Jeremy Fitzhardinge
2007-03-07 20:56             ` Davide Libenzi
2007-03-07 21:26               ` Jeremy Fitzhardinge
2007-03-07 21:35                 ` Davide Libenzi
2007-03-07 21:48                   ` Linus Torvalds
2007-03-07 22:01                     ` Ulrich Drepper
2007-03-07 22:10                       ` Davide Libenzi
2007-03-16  5:16                         ` Ulrich Drepper
2007-03-16  6:31                           ` Davide Libenzi
2007-03-07 22:01                     ` Davide Libenzi
2007-03-07 22:14                   ` Jeremy Fitzhardinge
2007-03-07 22:21                     ` Davide Libenzi
2007-03-07 17:42       ` 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=Pine.LNX.4.64.0703070943180.12283@alien.or.mcafeemobile.com \
    --to=davidel@xmailserver.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®