From: Chris Wedgwood <cw@f00f.org>
To: linux-ia64@vger.kernel.org
Subject: Re: should ia64_spinlock_contention do backoff?
Date: Fri, 26 Mar 2004 23:41:10 +0000 [thread overview]
Message-ID: <20040326234110.GA27824@dingdong.cryptoapps.com> (raw)
In-Reply-To: <200403251941.i2PJfrTH026392@napali.hpl.hp.com>
On Fri, Mar 26, 2004 at 09:16:52AM -0800, markw@osdl.org wrote:
> We have 4-way Itanium2 systems here. Is that large enough for
> testing?
It depends on the level of lock contention and what the remote memory
latency is (well, essentially how quickly you can bounce cachelines
about). As other people have mentioned SGI has tested this on much
larger configurations without seeing much incentive to use it.
As a general principal I think getting lock contention down is more
worthwhile (but very much harder usually).
Does anyone have any idea what locks are most heavily contented for
ia64 right now? John?
--cw
next prev parent reply other threads:[~2004-03-26 23:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 19:41 should ia64_spinlock_contention do backoff? David Mosberger
2004-03-25 20:06 ` John Hawkes
2004-03-25 22:13 ` Keith Owens
2004-03-25 22:28 ` David Mosberger
2004-03-26 17:16 ` markw
2004-03-26 23:41 ` Chris Wedgwood [this message]
2004-03-26 23:44 ` David Mosberger
2004-03-27 0:14 ` Chen, Kenneth W
2004-03-28 2:37 ` John Hawkes
2004-03-28 19:23 ` Matthew Wilcox
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=20040326234110.GA27824@dingdong.cryptoapps.com \
--to=cw@f00f.org \
--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