From: Ulrich Drepper <drepper@redhat.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: "Hu, Boris" <boris.hu@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Split futex global spinlock futex_lock
Date: Wed, 10 Sep 2003 00:36:07 -0700 [thread overview]
Message-ID: <3F5ED467.2030103@redhat.com> (raw)
In-Reply-To: <20030910064727.GN4306@holomorphy.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
William Lee Irwin III wrote:
> This looks nice and straightforward. How much did it speed up the
> benchmarks?
I just tested it on a UP P4 HT machine. I wouldn't expect much
difference here, bigger machines should show more (I'll try to get
things to work on my 4p machine). Volano performance increased by a bit
(~1%) but this is close to the error range.
Before: about 15479 messages per second
Now: about 15615 messages per second
The glibc test suite still passes so the code should be fine.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/XtRn2ijCOnn/RHQRAs+3AKCJ5C2WafltO9mCUiOfrw6ADiqCwACfQ3lc
b2z6DNKQqQz1X3/DreZIdpc=
=ILjm
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-09-10 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 5:23 [PATCH] Split futex global spinlock futex_lock Hu, Boris
2003-09-10 6:47 ` William Lee Irwin III
2003-09-10 7:36 ` Ulrich Drepper [this message]
2003-09-10 9:36 ` Ulrich Drepper
2003-09-10 10:23 ` Jamie Lokier
2003-09-10 11:07 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2003-09-11 7:02 Hu, Boris
2003-09-15 15:07 ` Rusty Russell
2003-09-16 4:48 ` Ulrich Drepper
2003-09-16 11:11 ` Jamie Lokier
2003-09-16 11:04 ` Jamie Lokier
2003-09-17 1:55 ` Rusty Russell
2003-09-16 7:31 Hu, Boris
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=3F5ED467.2030103@redhat.com \
--to=drepper@redhat.com \
--cc=boris.hu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.