From: Andrew Morton <akpm@linux-foundation.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, John Stultz <johnstul@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [patch, v2.6.22-rc6] sys_time() speedup
Date: Mon, 25 Jun 2007 15:15:08 -0700 [thread overview]
Message-ID: <20070625151508.86fa3778.akpm@linux-foundation.org> (raw)
In-Reply-To: <200706252309.47467.zippel@linux-m68k.org>
On Mon, 25 Jun 2007 23:09:46 +0200
Roman Zippel <zippel@linux-m68k.org> wrote:
> Hi,
>
> On Monday 25 June 2007, Ingo Molnar wrote:
>
> > the patch improves the sysbench OLTP macrobenchmark significantly:
>
> Has that any real practical relevance?
Interesting question. The patch adds a new test-n-branch to gettimeofday()
so if gettimeofday() is used much more frequently than time(), we lose.
> > @@ -373,6 +376,20 @@ void do_gettimeofday (struct timeval *tv
> >
> > tv->tv_sec = sec;
> > tv->tv_usec = usec;
> > +
> > + /*
> > + * Make sure xtime.tv_sec [returned by sys_time()] always
> > + * follows the gettimeofday() result precisely. This
> > + * condition is extremely unlikely, it can hit at most
> > + * once per second:
> > + */
> > + if (unlikely(xtime.tv_sec != tv->tv_sec)) {
> > + unsigned long flags;
> > +
> > + write_seqlock_irqsave(&xtime_lock);
> > + update_wall_time();
> > + write_seqlock_irqrestore(&xtime_lock);
> > + }
> > }
> >
> > EXPORT_SYMBOL(do_gettimeofday);
>
> Is this the do_gettimeofday() inside CONFIG_TIME_INTERPOLATION?
Yes.
> What did you test?
> There can be many ways to read the clock, do you want to put this hook
> everywhere?
Yeah, it isn't immediately obvious (to this little black duck) why similar
fixups weren't needed in timekeeping.c.
next prev parent reply other threads:[~2007-06-25 22:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 20:06 [patch, v2.6.22-rc6] sys_time() speedup Ingo Molnar
2007-06-25 21:09 ` Roman Zippel
2007-06-25 21:17 ` Jesper Juhl
2007-06-25 22:00 ` Roman Zippel
2007-06-25 22:20 ` Jesper Juhl
2007-06-25 22:49 ` Roman Zippel
2007-06-26 16:18 ` Ingo Molnar
2007-06-26 16:39 ` Roman Zippel
2007-06-26 16:49 ` Andrea Arcangeli
2007-06-26 17:13 ` Ray Lee
2007-06-27 0:15 ` Andrea Arcangeli
2007-06-26 17:08 ` Roman Zippel
2007-06-26 17:35 ` Andrew Morton
2007-06-25 22:15 ` Andrew Morton [this message]
2007-06-26 2:20 ` Stephen Rothwell
2007-06-26 15:26 ` Ingo Molnar
2007-06-26 17:14 ` Andrew Morton
2007-06-27 0:22 ` Andrea Arcangeli
2007-06-26 15:43 ` Andrea Arcangeli
2007-06-26 17:36 ` Andrew Morton
2007-06-25 22:02 ` Eric Dumazet
2007-06-26 0:22 ` Mark Lord
2007-06-26 14:58 ` Ingo Molnar
2007-06-26 16:59 ` john stultz
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=20070625151508.86fa3778.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox