From: John Hesterberg <jh@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Scalability enhancements for gettimeofday
Date: Wed, 02 Jun 2004 20:58:26 +0000 [thread overview]
Message-ID: <20040602205826.GB4680@sgi.com> (raw)
In-Reply-To: <200405201205.57930.clameter@sgi.com>
On Wed, Jun 02, 2004 at 10:33:39AM -0700, David Mosberger wrote:
> Christoph> Also the fast system call handler for sys_gettimeofday()
> Christoph> can only improve scalability if the ITC is the basis for
> Christoph> gettimeofday which is also never the case on Altix SN2
> Christoph> systems.
>
> Does this really make a substantial difference? My guess is no and,
> if so, I'd rather not add any more #ifdefs.
It also only helps SN2 kernels and not generic kernels.
I don't think this is they key part of the patch,
so unless we see some compelling performance evidence,
I'd agree it seems better to leave out the #ifdef.
John
next prev parent reply other threads:[~2004-06-02 20:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 19:05 Scalability enhancements for gettimeofday Christoph Lameter
2004-06-02 17:33 ` David Mosberger
2004-06-02 20:58 ` John Hesterberg [this message]
2004-06-03 2:38 ` Jack Steiner
2004-06-03 4:56 ` Christoph Lameter
2004-06-03 16:28 ` Christoph Lameter
2004-06-03 20:04 ` Chris Wedgwood
2004-06-04 6:29 ` David Mosberger
2004-06-04 14:26 ` Christoph Lameter
2004-06-05 5:12 ` David Mosberger
2004-06-07 17:46 ` Christoph Lameter
2004-06-07 18:14 ` David Mosberger
2004-06-07 20:24 ` Christoph Lameter
2004-06-07 20:55 ` David Mosberger
2004-06-07 22:48 ` Christoph Lameter
2004-06-07 23:02 ` David Mosberger
2004-06-08 4:08 ` Christoph Lameter
2004-06-08 4:33 ` David Mosberger
2004-06-08 5:59 ` Christoph Lameter
2004-06-08 6:06 ` David Mosberger
2004-06-08 7:11 ` Christoph Lameter
2004-06-08 18:02 ` David Mosberger
2004-06-08 18:32 ` Christoph Lameter
2004-06-08 21:38 ` David Mosberger
2004-06-08 21:48 ` Christoph Lameter
2004-06-08 22:13 ` David Mosberger
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=20040602205826.GB4680@sgi.com \
--to=jh@sgi.com \
--cc=linux-ia64@vger.kernel.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