From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] interesting timing tests
Date: Mon, 21 Jun 2010 14:11:00 -0700 [thread overview]
Message-ID: <20100621211101.0405C5B3E@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Fri, 18 Jun 2010 19:26:25 EDT." <ce0445185b53080d4414a74250d32458@coraid.com>
On Fri, 18 Jun 2010 19:26:25 EDT erik quanstrom <quanstro@labs.coraid.com> wrote:
> note the extreme system time on the 16 processor machine
Could this be due to memory contention caused by spinlocks?
While locks are spinning they eat up memory bandwidth which
slows down everyone's memory accesses (including the one who
is trying to finish its work while holding the spinlock).
And the more processors contend, the worse it gets....
How well does plan9 lock() scale with the number of processor?
Since this is analogous to accessing a CSMA network, one can
use a similar algorithm to ameliorate the bandwidth problem:
if you didn't get the lock, assume it will be a little while
before you can get it so you might as well backoff. There is
an old paper that talks about this.
Or it could simply be due to caching behaviour, if everyone
is accessing/mutating the same pages at the same time.
next prev parent reply other threads:[~2010-06-21 21:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 23:26 erik quanstrom
2010-06-19 13:42 ` Richard Miller
2010-06-20 1:36 ` erik quanstrom
2010-06-20 7:44 ` Richard Miller
2010-06-20 12:45 ` erik quanstrom
2010-06-20 16:51 ` Richard Miller
2010-06-20 21:55 ` erik quanstrom
2010-06-21 1:41 ` erik quanstrom
2010-06-21 3:46 ` Venkatesh Srinivas
2010-06-21 14:40 ` erik quanstrom
2010-06-21 16:42 ` Venkatesh Srinivas
2010-06-21 16:43 ` erik quanstrom
2010-06-21 21:11 ` Bakul Shah [this message]
2010-06-21 21:21 ` erik quanstrom
2010-06-21 21:47 ` Bakul Shah
2010-06-21 22:16 ` erik quanstrom
2010-06-22 3:24 ` Lawrence E. Bakst
2010-06-23 1:09 ` erik quanstrom
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=20100621211101.0405C5B3E@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.com \
--cc=9fans@9fans.net \
/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).