From: Artem Bityutskiy <dedekind1@gmail.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Alexander Shishkin <virtuoso@slind.org>,
Thomas Gleixner <tglx@linutronix.de>,
Kyle Moffett <kyle@moffetthome.net>,
Valdis.Kletnieks@vt.edu, LKML <linux-kernel@vger.kernel.org>,
John Stultz <johnstul@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Kay Sievers <kay.sievers@vrfy.org>, Greg KH <gregkh@suse.de>,
Chris Friesen <chris.friesen@genband.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCHv6 0/7] system time changes notification
Date: Thu, 18 Nov 2010 15:08:20 +0200 [thread overview]
Message-ID: <1290085700.2270.7.camel@localhost> (raw)
In-Reply-To: <alpine.DEB.2.00.1011171130210.1595@davide-lnx1>
On Wed, 2010-11-17 at 12:42 -0800, Davide Libenzi wrote:
> On Wed, 17 Nov 2010, Alexander Shishkin wrote:
>
> > > But what you folks really want for this stuff is an extension to
> > > timerfd as you want to be able to poll, right?
> > >
> > > So what about the following:
> > >
> > > Add a new flag TDF_NOTIFY_CLOCK_WAS_SET to the timerfd flags. Now this
> > > flag adds the timer to a separate list, which gets woken up when the
> > > clock is set.
> > >
> > > No new syscall, just a few lines of code in fs/timerfd.c and
> > > clock_was_set().
> > >
> > > Thoughts ?
> >
> > Something like this (sans ugliness)?
>
> Oh, gosh, please. This is interface-multiplexing-a-palooza.
> It should be decided if the feature makes sense, and then have proper
> interface, instead of multiplexing unrelated insterfaces.
> This is a sort of system-event-report pattern. What is wrong with using a
> netlink-based transport for those kind of things?
Could you please explain in more details what is the problem?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-11-18 13:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 19:29 [PATCHv6 0/7] system time changes notification Alexander Shishkin
2010-11-11 19:29 ` [PATCHv6 1/7] notify userspace about time changes Alexander Shishkin
2010-11-11 20:55 ` Arnd Bergmann
2010-11-11 19:29 ` [PATCHv6 2/7] wire up sys_time_change_notify() on ARM Alexander Shishkin
2010-11-11 19:29 ` [PATCHv6 3/7] wire up sys_time_change_notify() on x86 Alexander Shishkin
2010-11-11 19:29 ` [PATCHv6 4/7] wire up sys_time_change_notify() on ia64 Alexander Shishkin
2010-11-11 19:29 ` Alexander Shishkin
2010-11-11 19:30 ` [PATCHv6 5/7] wire up sys_time_change_notify() on s390 Alexander Shishkin
2010-11-11 19:30 ` [PATCHv6 6/7] wire up sys_time_change_notify() on powerpc Alexander Shishkin
2010-11-11 19:30 ` Alexander Shishkin
2010-11-11 19:30 ` [PATCHv6 7/7] wire up sys_time_change_notify() on blackfin Alexander Shishkin
2010-11-11 20:28 ` [PATCHv6 0/7] system time changes notification Valdis.Kletnieks
2010-11-11 20:51 ` Alexander Shishkin
2010-11-11 21:16 ` Thomas Gleixner
2010-11-11 22:11 ` Kyle Moffett
2010-11-11 22:36 ` john stultz
2010-11-11 23:19 ` Kyle Moffett
2010-11-11 23:41 ` john stultz
2010-11-11 23:45 ` john stultz
2010-11-11 22:50 ` Thomas Gleixner
2010-11-12 2:35 ` Davide Libenzi
2010-11-17 19:06 ` Alexander Shishkin
2010-11-17 20:42 ` Davide Libenzi
2010-11-17 21:29 ` Alexander Shishkin
2010-11-17 21:34 ` Kay Sievers
2010-11-18 15:59 ` Alexander Shishkin
2010-11-17 21:46 ` Thomas Gleixner
2010-11-18 9:49 ` Alexander Shishkin
2010-11-18 13:08 ` Artem Bityutskiy [this message]
2010-11-12 9:25 ` Alan Cox
2010-11-12 10:53 ` Richard Cochran
2010-11-12 11:25 ` Alan Cox
2010-11-12 10:47 ` Kay Sievers
2010-11-12 12:30 ` Alexander Shishkin
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=1290085700.2270.7.camel@localhost \
--to=dedekind1@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=chris.friesen@genband.com \
--cc=davidel@xmailserver.org \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=kay.sievers@vrfy.org \
--cc=kirill@shutemov.name \
--cc=kyle@moffetthome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=virtuoso@slind.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 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.