From: Thomas Gleixner <tglx@linutronix.de>
To: Michael Kerrisk <mtk-manpages@gmx.net>
Cc: "Davide Libenzi" <davidel@xmailserver.org>,
"Ulrich Drepper" <drepper@redhat.com>,
geoff@gclare.org.uk, lkml <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Christoph Hellwig" <hch@lst.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"Randy Dunlap" <rdunlap@xenotime.net>,
vda.linux@googlemail.com,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Lee Schermerhorn" <Lee.Schermerhorn@hp.com>,
"David Härdeman" <david@hardeman.nu>
Subject: Re: RFC: A revised timerfd API
Date: Sat, 22 Sep 2007 19:10:02 +0200 [thread overview]
Message-ID: <1190481002.4035.51.camel@chaos> (raw)
In-Reply-To: <46F514C9.5010208@gmx.net>
Michael,
On Sat, 2007-09-22 at 15:12 +0200, Michael Kerrisk wrote:
> Davide, Andrew, Linus, et al.
>
> At the start of this thread
> (http://thread.gmane.org/gmane.linux.kernel/581115 ), I proposed 4
> alternatives to Davide's original timerfd API. Based on the feedback in
> that thread (and one or two earlier comments):
>
> Let's dismiss option (a), since it is an unlovely multiplexing interface.
>
> Option (b) seems a viable. The most notable concern was from Thomas
> Gleixner, that we might end up duplicating code from the POSIX timers API
> within the timerfd API -- some eventual refactoring might mitigate this
> problem.
It should be possible to use the timerfd syscalls as wrappers for the
posix timer implementation and add the discussed SIGEV_TIMERFD only
internally in the kernel to signal the posix timer code new delivery
mechanism.
tglx
next prev parent reply other threads:[~2007-09-22 17:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 7:27 RFC: A revised timerfd API Michael Kerrisk
2007-09-18 7:30 ` Michael Kerrisk
2007-09-18 8:05 ` David Härdeman
2007-09-18 9:01 ` Michael Kerrisk
2007-09-18 9:27 ` Thomas Gleixner
2007-09-18 9:10 ` Thomas Gleixner
2007-09-18 9:30 ` Michael Kerrisk
2007-09-18 9:42 ` Thomas Gleixner
2007-09-18 11:08 ` Michael Kerrisk
2007-09-18 11:30 ` Thomas Gleixner
2007-09-18 13:13 ` David Härdeman
2007-09-22 13:03 ` Michael Kerrisk
2007-09-18 16:51 ` Davide Libenzi
2007-09-22 13:12 ` Michael Kerrisk
2007-09-22 14:32 ` Bernd Eckenfels
2007-09-22 16:07 ` Michael Kerrisk
2007-09-22 17:05 ` Thomas Gleixner
2007-09-22 23:37 ` David Härdeman
2007-09-22 17:10 ` Thomas Gleixner [this message]
2007-09-22 21:07 ` Davide Libenzi
2007-09-22 21:26 ` Thomas Gleixner
2007-09-22 23:21 ` Davide Libenzi
2007-09-23 17:33 ` Michael Kerrisk
2007-09-23 18:33 ` Davide Libenzi
2007-09-23 18:41 ` Davide Libenzi
2007-09-23 19:03 ` Michael Kerrisk
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=1190481002.4035.51.camel@chaos \
--to=tglx@linutronix.de \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@hardeman.nu \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=geoff@gclare.org.uk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.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.