From: Thomas Gleixner <tglx@linutronix.de>
To: Michael Kerrisk <mtk.linux.lists@gmail.com>
Cc: "Bernd Eckenfels" <ecki@lina.inka.de>,
linux-kernel@vger.kernel.org,
"Ulrich Drepper" <drepper@redhat.com>,
geoff@gclare.org.uk, "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>,
mtk-manpages@gmx.net
Subject: Re: RFC: A revised timerfd API
Date: Sat, 22 Sep 2007 19:05:17 +0200 [thread overview]
Message-ID: <1190480717.4035.45.camel@chaos> (raw)
In-Reply-To: <517f3f820709220907l4c4e693di3df6942bdca5bcfa@mail.gmail.com>
On Sat, 2007-09-22 at 18:07 +0200, Michael Kerrisk wrote:
> Hello Bernd,
>
> Please don't trim the CC list when replying! I nearly did not see
> your reply, and others will have missed it also.
Yup.
> On 9/22/07, Bernd Eckenfels <ecki@lina.inka.de> wrote:
> > In article <46F514C9.5010208@gmx.net> you wrote:
> > > 1. This design stretches the POSIX timers API in strange
> > > ways.
> >
> > Maybe it is possible to reimplement the POSIX API in usermode using the
> > kernel's FD implementation?
Yikes.
> It's a clever idea... Without thinking on it too long, I'm not sure
> whether or not there might be some details which would make this
> difficult.
You'd need be quite masochistic to start such a project. The POSIX timer
API consists mostly of corner cases and I doubt that you get them even
halfway under control in a pure user space implementation.
It would be a rather huge performance penalty as well. You need at least
two user space context switches to get the most simple cases resolved.
> > (and drop the posix support from kernel)
>
> However we couldn't drop POSIX support from the kernel, because that
> would break the ABI.
True. So there is no point in reinventing the wheel.
tglx
next prev parent reply other threads:[~2007-09-22 17:05 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 [this message]
2007-09-22 23:37 ` David Härdeman
2007-09-22 17:10 ` Thomas Gleixner
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=1190480717.4035.45.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=drepper@redhat.com \
--cc=ecki@lina.inka.de \
--cc=geoff@gclare.org.uk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=mtk.linux.lists@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox