From: Ingo Molnar <mingo@elte.hu>
To: Roland McGrath <roland@redhat.com>
Cc: Casey Dahlin <cdahlin@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Oleg Nesterov <oleg@redhat.com>,
Davide Libenzi <davidel@xmailserver.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RESEND][RFC PATCH v2] waitfd
Date: Wed, 7 Jan 2009 21:58:16 +0100 [thread overview]
Message-ID: <20090107205816.GC4597@elte.hu> (raw)
In-Reply-To: <20090107205322.5F8C7FC3E0@magilla.sf.frob.com>
* Roland McGrath <roland@redhat.com> wrote:
> New syscall should have gone to linux-api, I think.
>
> Do we really need another one for this? How about using signalfd plus
> setting the child's exit_signal to a queuing (SIGRTMIN+n) signal instead
> of SIGCHLD? It's slightly more magical for the userland process to know
> to do that (fork -> clone SIGRTMIN). But compared to adding a syscall
> we don't really have to add, maybe better.
hm, i think it's cleaner conceptually than trying to wrap this into
signalfd. Since we already have:
#define __NR_signalfd 321
#define __NR_timerfd_create 322
#define __NR_timerfd_settime 325
#define __NR_timerfd_gettime 326
#define __NR_signalfd4 327
is one more really such an issue?
Ingo
next prev parent reply other threads:[~2009-01-07 20:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 18:11 [RFC PATCH v2] waitfd Casey Dahlin
2009-01-06 18:27 ` Alan Cox
2009-01-06 18:31 ` Randy Dunlap
2009-01-06 18:45 ` Casey Dahlin
2009-01-06 18:50 ` Randy Dunlap
2009-01-06 18:48 ` Andi Kleen
2009-01-06 19:07 ` [RESEND][RFC " Casey Dahlin
2009-01-07 12:34 ` Ingo Molnar
2009-01-07 13:05 ` Casey Dahlin
2009-01-07 15:00 ` Ingo Molnar
2009-01-07 17:19 ` Oleg Nesterov
2009-01-07 17:24 ` Ingo Molnar
2009-01-07 17:52 ` Davide Libenzi
2009-01-07 20:38 ` Casey Dahlin
2009-01-10 14:47 ` Scott James Remnant
2009-01-10 21:14 ` Casey Dahlin
2009-01-10 21:20 ` Scott James Remnant
2009-01-10 22:08 ` Casey Dahlin
2009-01-10 22:31 ` Oleg Nesterov
2009-01-10 22:37 ` Casey Dahlin
2009-01-10 22:46 ` Oleg Nesterov
2009-01-07 20:53 ` Roland McGrath
2009-01-07 20:58 ` Ingo Molnar [this message]
2009-01-07 21:05 ` Davide Libenzi
2009-01-07 21:50 ` Ingo Molnar
2009-01-07 21:02 ` Ulrich Drepper
2009-01-08 14:32 ` Oleg Nesterov
2009-01-08 19:35 ` Roland McGrath
2009-01-08 20:36 ` Casey Dahlin
2009-01-08 21:39 ` Oleg Nesterov
2009-01-10 14:52 ` Scott James Remnant
2009-01-10 16:19 ` Oleg Nesterov
2009-01-10 17:09 ` Scott James Remnant
2009-01-10 18:21 ` Oleg Nesterov
2009-01-10 18:46 ` Scott James Remnant
2009-01-10 14:50 ` Scott James Remnant
2009-01-10 21:20 ` Casey Dahlin
2009-01-08 22:04 ` Michael Kerrisk
2009-01-10 14:09 ` Scott James Remnant
2009-01-10 14:45 ` Scott James Remnant
2009-01-10 15:57 ` Oleg Nesterov
2009-01-10 17:07 ` Scott James Remnant
2009-01-10 18:13 ` Oleg Nesterov
2009-01-10 20:13 ` Scott James Remnant
2009-01-10 22:24 ` Oleg Nesterov
2009-01-10 23:14 ` Davide Libenzi
2009-01-10 22:25 ` Casey Dahlin
2009-01-10 23:11 ` Davide Libenzi
2011-03-02 1:37 ` Denys Vlasenko
2011-03-02 13:55 ` Oleg Nesterov
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=20090107205816.GC4597@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=cdahlin@redhat.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=randy.dunlap@oracle.com \
--cc=roland@redhat.com \
/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