From: Ingo Molnar <mingo@elte.hu>
To: P@draigBrady.com
Cc: netdev@oss.sgi.com, Andrea Arcangeli <andrea@suse.de>
Subject: Re: gettimeofday scalability
Date: Tue, 5 Oct 2004 21:18:58 +0200 [thread overview]
Message-ID: <20041005191858.GA14082@elte.hu> (raw)
In-Reply-To: <4162CD76.4070204@draigBrady.com>
* P@draigBrady.com <P@draigBrady.com> wrote:
> In particular I was wondering about reducing the overhead of
> calling do_gettimeofday.
> 2.6.8.1 uses seqlock, which contains the comment that it's not as
> cache friendly as brlock.
that comment is way too modest! Seqlocks are very cache-friendly in the
read path. There is no reason to use brlocks anymore for fixed-frequency
writers like the timer seqlock. (writers can starve seqlock readers but
in the timer case the writers occur only once every 1 msec.)
so please benchmark 2.6, it should scale linearly in this area.
Ingo
prev parent reply other threads:[~2004-10-05 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 16:36 gettimeofday scalability P
2004-10-05 18:35 ` David S. Miller
2004-10-05 18:48 ` Stephen Hemminger
2004-10-05 18:55 ` Andrea Arcangeli
2004-10-05 19:16 ` P
2004-10-05 19:35 ` Andrea Arcangeli
2004-10-05 19:18 ` Ingo Molnar [this message]
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=20041005191858.GA14082@elte.hu \
--to=mingo@elte.hu \
--cc=P@draigBrady.com \
--cc=andrea@suse.de \
--cc=netdev@oss.sgi.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 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.