[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1011172244470.2900@localhost6.localdomain6>
Date: Wed, 17 Nov 2010 22:46:48 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Alexander Shishkin <virtuoso@...nd.org>
cc: Davide Libenzi <davidel@...ilserver.org>,
Kyle Moffett <kyle@...fetthome.net>, Valdis.Kletnieks@...edu,
LKML <linux-kernel@...r.kernel.org>,
John Stultz <johnstul@...ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
Kay Sievers <kay.sievers@...y.org>, Greg KH <gregkh@...e.de>,
Chris Friesen <chris.friesen@...band.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Kirill A. Shutemov" <kirill@...temov.name>
Subject: Re: [PATCHv6 0/7] system time changes notification
On Wed, 17 Nov 2010, Alexander Shishkin wrote:
> On Wed, Nov 17, 2010 at 12:42:52PM -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.
>
> Thomas made a suggestion, I came up with how it might look like so that
Yeah, I made the suggestion in the first place and I regretted it when
Davide told me that I'm nuts :)
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists