From: Oleg Nesterov <oleg@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Andrey Vagin <avagin@openvz.org>,
linux-kernel@vger.kernel.org, criu@openvz.org,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
David Howells <dhowells@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Pavel Emelyanov <xemul@parallels.com>,
Cyrill Gorcunov <gorcunov@openvz.org>
Subject: Re: [PATCH 2/3] signalfd: add ability to choose a private or shared queue
Date: Fri, 8 Feb 2013 20:12:56 +0100 [thread overview]
Message-ID: <20130208191256.GB13674@redhat.com> (raw)
In-Reply-To: <CAKgNAkjq3hVjYA3pVdBhyiFi1PbvXc_mOyvx_FaY67PmAifBOQ@mail.gmail.com>
On 02/08, Michael Kerrisk (man-pages) wrote:
>
> I'd greatly prefer names that really say what these things are. Thus:
>
> SFD_PROCESS_QUEUE + SFD_THREAD_QUEUE
> or
> SFD_PROCESS_WIDE_QUEUE + SFD_PER_THREAD_QUEUE
> or
> SFD_PROCESS_Q + SFD_THREAD_Q
> or
> [some consistent variation of the above]
I am fine either way.
But again, perhaps ioctl/ptrace is better.
Oleg.
next prev parent reply other threads:[~2013-02-08 19:14 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 10:15 [PATCH 0/3] signalfd: a kernel interface for dumping pending signals Andrey Vagin
2013-01-22 10:15 ` Andrey Vagin
2013-01-22 10:15 ` [PATCH 1/3] signal: add a helper for dequeuing signals from a specified queue Andrey Vagin
2013-01-22 10:15 ` Andrey Vagin
2013-02-05 12:00 ` [PATCH 1/3] signal: add a helper for dequeuing signals from a specified queue (v2) Andrey Vagin
2013-02-05 12:00 ` Andrey Vagin
2013-01-22 10:15 ` [PATCH 2/3] signalfd: add ability to choose a private or shared queue Andrey Vagin
2013-01-22 10:15 ` Andrey Vagin
2013-02-07 18:17 ` Oleg Nesterov
2013-02-08 0:35 ` Michael Kerrisk (man-pages)
2013-02-08 0:35 ` Michael Kerrisk (man-pages)
2013-02-08 19:12 ` Oleg Nesterov [this message]
2013-01-22 10:15 ` [PATCH 3/3] signalfd: add ability to read siginfo-s without dequeuing signals Andrey Vagin
2013-01-29 19:03 ` [PATCH 3/3] signalfd: add ability to read siginfo-s without dequeuing signals (v2) Andrey Vagin
[not found] ` <CAKgNAkgQA=zK=2ZnytPFU=DH6jr0sja0iy6K+j6c7unheLFniQ@mail.gmail.com>
2013-02-02 7:15 ` Andrey Wagin
2013-02-02 7:15 ` Andrey Wagin
2013-02-07 17:34 ` Oleg Nesterov
2013-02-07 17:34 ` Oleg Nesterov
2013-02-07 21:13 ` Andrey Wagin
2013-02-07 21:13 ` Andrey Wagin
2013-02-08 0:51 ` Michael Kerrisk (man-pages)
2013-02-08 19:10 ` Oleg Nesterov
2013-02-08 20:15 ` Michael Kerrisk (man-pages)
2013-02-08 20:15 ` Michael Kerrisk (man-pages)
2013-02-09 18:22 ` Oleg Nesterov
2013-02-09 22:53 ` Michael Kerrisk (man-pages)
2013-02-09 22:53 ` Michael Kerrisk (man-pages)
2013-02-10 10:04 ` [CRIU] " Andrew Vagin
2013-02-10 10:04 ` Andrew Vagin
2013-02-11 16:47 ` Oleg Nesterov
2013-02-11 16:47 ` Oleg Nesterov
2013-02-10 10:07 ` Andrew Vagin
2013-02-10 10:07 ` Andrew Vagin
2013-02-11 9:29 ` Denys Vlasenko
2013-02-11 10:59 ` [CRIU] " Andrew Vagin
2013-02-11 10:59 ` Andrew Vagin
2013-02-11 14:46 ` Denys Vlasenko
2013-02-11 14:46 ` Denys Vlasenko
2013-02-11 14:53 ` Pavel Emelyanov
2013-02-11 14:53 ` Pavel Emelyanov
2013-02-11 17:25 ` Denys Vlasenko
2013-02-11 17:25 ` Denys Vlasenko
2013-02-12 14:50 ` Pavel Emelyanov
2013-02-12 14:50 ` Pavel Emelyanov
2013-01-23 4:19 ` [PATCH 0/3] signalfd: a kernel interface for dumping pending signals Michael Kerrisk (man-pages)
2013-01-23 11:03 ` Andrew Vagin
2013-01-23 11:03 ` Andrew Vagin
2013-01-23 11:03 ` Andrew Vagin
2013-01-23 12:11 ` Michael Kerrisk (man-pages)
2013-01-23 12:11 ` Michael Kerrisk (man-pages)
2013-01-23 13:03 ` Andrew Vagin
2013-01-23 13:03 ` Andrew Vagin
2013-01-23 13:03 ` Andrew Vagin
2013-02-07 18:20 ` Oleg Nesterov
2013-02-07 18:20 ` Oleg Nesterov
2013-02-08 0:36 ` Michael Kerrisk (man-pages)
2013-02-08 0:36 ` Michael Kerrisk (man-pages)
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=20130208191256.GB13674@redhat.com \
--to=oleg@redhat.com \
--cc=avagin@openvz.org \
--cc=criu@openvz.org \
--cc=dhowells@redhat.com \
--cc=gorcunov@openvz.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.