From: Matthew Wilcox <willy@debian.org>
To: "Van Maren, Kevin" <kevin.vanmaren@unisys.com>
Cc: "'Linus Torvalds '" <torvalds@transmeta.com>,
"'Jeremy Fitzhardinge '" <jeremy@goop.org>,
"'William Lee Irwin III '" <wli@holomorphy.com>,
"'linux-ia64@linuxia64.org '" <linux-ia64@linuxia64.org>,
"'Linux Kernel List '" <linux-kernel@vger.kernel.org>,
"'rusty@rustcorp.com.au '" <rusty@rustcorp.com.au>,
"'dhowells@redhat.com '" <dhowells@redhat.com>,
"'mingo@elte.hu '" <mingo@elte.hu>
Subject: Re: [Linux-ia64] reader-writer livelock problem
Date: Fri, 8 Nov 2002 17:52:19 +0000 [thread overview]
Message-ID: <20021108175219.L12011@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3FAD1088D4556046AEC48D80B47B478C0101F4EB@usslc-exch-4.slc.unisys.com>; from kevin.vanmaren@unisys.com on Fri, Nov 08, 2002 at 11:41:57AM -0600
On Fri, Nov 08, 2002 at 11:41:57AM -0600, Van Maren, Kevin wrote:
> processor to acquire/release the lock once. So with 32 processors
> contending for the lock, at 1us per cache-cache transfer (picked
if you have 32 processors contending for the same spinlock, you have
bigger problems.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-11-08 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 17:41 [Linux-ia64] reader-writer livelock problem Van Maren, Kevin
2002-11-08 17:52 ` Matthew Wilcox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 20:24 Van Maren, Kevin
2002-11-08 20:17 Van Maren, Kevin
2002-11-08 20:39 ` Matthew Wilcox
2002-11-08 18:05 Van Maren, Kevin
2002-11-08 19:19 ` Matthew Wilcox
2002-11-08 19:26 ` David Mosberger
[not found] <3FAD1088D4556046AEC48D80B47B478C0101F4E7@usslc-exch-4.slc.unisys.com>
2002-11-08 3:51 ` William Lee Irwin III
2002-11-08 17:13 ` Jeremy Fitzhardinge
2002-11-08 17:25 ` Linus Torvalds
2002-11-08 17:28 ` Linus Torvalds
2002-11-08 17:38 ` Jeremy Fitzhardinge
2002-11-08 17:43 ` David Howells
2002-11-08 17:57 ` Linus Torvalds
2002-11-09 2:48 ` Rusty Russell
2002-11-09 4:36 ` William Lee Irwin III
2002-11-08 17:34 ` David Howells
2002-11-08 17:54 ` David Howells
2002-11-08 17:55 ` Stephen Hemminger
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=20021108175219.L12011@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=dhowells@redhat.com \
--cc=jeremy@goop.org \
--cc=kevin.vanmaren@unisys.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
--cc=wli@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).