[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1372741852.7363.110.camel@marge.simpson.net>
Date: Tue, 02 Jul 2013 07:10:52 +0200
From: Mike Galbraith <bitbucket@...ine.de>
To: paulmck@...ux.vnet.ibm.com
Cc: Josh Triplett <josh@...htriplett.org>,
linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...ymtl.ca, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, dhowells@...hat.com,
edumazet@...gle.com, darren@...art.com, fweisbec@...il.com,
sbw@....edu
Subject: Re: [PATCH RFC nohz_full v2 2/7] nohz_full: Add rcu_dyntick data
for scalable detection of all-idle state
On Mon, 2013-07-01 at 12:16 -0700, Paul E. McKenney wrote:
> On Mon, Jul 01, 2013 at 11:34:13AM -0700, Josh Triplett wrote:
> > > > This also naturally raises the question "How can we let userspace get
> > > > accurate time without forcing a timer tick?".
> > >
> > > We don't. ;-)
> >
> > We don't currently, hence my question about how we can. :)
>
> Per-CPU atomic clocks?
Great idea, who needs timekeeping code.
http://www.euronews.com/2013/04/02/swiss-sets-sights-on-miniscule-atomic-clock/
-Mike
--
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