public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: should ia64_spinlock_contention do backoff?
Date: Thu, 25 Mar 2004 19:41:53 +0000	[thread overview]
Message-ID: <200403251941.i2PJfrTH026392@napali.hpl.hp.com> (raw)

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.

	--david

             reply	other threads:[~2004-03-25 19:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 19:41 David Mosberger [this message]
2004-03-25 20:06 ` should ia64_spinlock_contention do backoff? 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
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=200403251941.i2PJfrTH026392@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.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