public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: "Hu, Boris" <boris.hu@intel.com>,
	Jamie Lokier <jamie@shareable.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Split futex global spinlock futex_lock
Date: Mon, 15 Sep 2003 21:48:14 -0700	[thread overview]
Message-ID: <3F66960E.7010703@redhat.com> (raw)
In-Reply-To: <20030916010313.69E1F2C974@lists.samba.org>

Rusty Russell wrote:

> Uli, can we ask you for benchmarks with this change, too?

After these changes the code still works but I couldn't really measure
any differences to the code without the extra attributes.  This is on a
4p machine with 10 processes running in concurrently using mutexes and
condvars with 250 threads each.  This might be because either the hash
function is good or very bad (i.e., hashes all futexes in the same
bucket or far away).  I guess the extra attributes don't hurt.

-- 
--------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------


  reply	other threads:[~2003-09-16  4:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11  7:02 [PATCH] Split futex global spinlock futex_lock Hu, Boris
2003-09-15 15:07 ` Rusty Russell
2003-09-16  4:48   ` Ulrich Drepper [this message]
2003-09-16 11:11     ` Jamie Lokier
2003-09-16 11:04   ` Jamie Lokier
2003-09-17  1:55     ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2003-09-16  7:31 Hu, Boris
2003-09-10  5:23 Hu, Boris
2003-09-10  6:47 ` William Lee Irwin III
2003-09-10  7:36   ` Ulrich Drepper
2003-09-10  9:36 ` Ulrich Drepper
2003-09-10 10:23   ` Jamie Lokier
2003-09-10 11:07 ` Jamie Lokier

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=3F66960E.7010703@redhat.com \
    --to=drepper@redhat.com \
    --cc=boris.hu@intel.com \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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