From: Ulrich Drepper <drepper@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "Hu, Boris" <boris.hu@intel.com>
Subject: Re: [PATCH] Split futex global spinlock futex_lock
Date: Wed, 10 Sep 2003 02:36:57 -0700 [thread overview]
Message-ID: <3F5EF0B9.7020207@redhat.com> (raw)
In-Reply-To: <37FBBA5F3A361C41AB7CE44558C3448E01C0B69E@pdsmsx403.ccr.corp.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've run some tests on a 4p P4 HT machine. Some heavy futex using
benchmark code runs about 6% faster with the patch. So, despite the
reduced time the futex lock is actually taken after Jamie's patch the
separate locks still add benefits.
Plus, currently we do not allocate locks so that the futexes fall in
different buckets. To some extend this is possible and would be a
possible optimization if this patch goes in.
- --
- --------------. ,-. 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/XvC62ijCOnn/RHQRApUsAJ0RB/WsVZTgC31yIbAFL4KdMi8UcgCeI+Gv
uAVQQReC9Tl1g8HogsReVdA=
=vRBt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-09-10 9:37 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
2003-09-10 9:36 ` Ulrich Drepper [this message]
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=3F5EF0B9.7020207@redhat.com \
--to=drepper@redhat.com \
--cc=boris.hu@intel.com \
--cc=linux-kernel@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