From: "John Hawkes" <hawkes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: should ia64_spinlock_contention do backoff?
Date: Thu, 25 Mar 2004 20:06:46 +0000 [thread overview]
Message-ID: <001a01c412a4$c5562470$d7069aa3@PCJohn> (raw)
In-Reply-To: <200403251941.i2PJfrTH026392@napali.hpl.hp.com>
From: "David Mosberger" <davidm@napali.hpl.hp.com>
> Has anyone studied the impact of doing exponential backoff in
> ia64_spinlock_contention. My theory is that it wouldn't buy much _if_
> spinlocks always were in their own cachelines, but since they're not,
> not using backoff could cause extra cache-line bouncing. To be
> honest, I'd rather not spend time on this myself, since I don't have
> convenient access to large machines, but me thinks this is a question
> that's long overdue to have a proper answer.
We (at SGI) don't have definitive measurements on this, but it's On The List
of things to do.
I believe that for a NUMA system, one big problem with highly-contended
spinlocks is the relative unfairness of the more remote nodes as the waiters
race to see the spinlock freed and to be the first to reacquire it. In
extreme cases this unfairness becomes a near-starvation. A backoff algorithm
would likely produce more fairness in these high-contention cases, although at
the expense of potentially lengthening the wait-times for the shortest
waiters.
John Hawkes
next prev parent reply other threads:[~2004-03-25 20:06 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 [this message]
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
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='001a01c412a4$c5562470$d7069aa3@PCJohn' \
--to=hawkes@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