From: Pierre Peiffer <pierre.peiffer@bull.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
Ulrich Drepper <drepper@redhat.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH 2.6.20-rc4 0/4] futexes functionalities and improvements
Date: Tue, 16 Jan 2007 09:34:50 +0100 [thread overview]
Message-ID: <45AC8E2A.3060708@bull.net> (raw)
In-Reply-To: <20070112075816.GA23341@elte.hu>
Hi,
Ingo Molnar a écrit :
> yeah. As an alternative, it might be a good idea to pthread-ify
> hackbench.c - that should replicate the Volano workload pretty
> accurately. I've attached hackbench.c. (it's process based right now, so
> it wont trigger contended futex ops)
Ok, thanks. I've adapted your test, Ingo, and do some measures. (I've only
replaced fork with pthread_create, I didn't use condvar or barrier for the first
synchronization).
The modified hackbench is available here:
http://www.bullopensource.org/posix/pi-futex/hackbench_pth.c
I've run this bench 1000 times with pipe and 800 groups.
Here are the results:
Test1 - with simple list (i.e. without any futex patches)
=========================================================
Iterations=1000
Latency (s) min max avg stddev
26.67 27.89 27.14 0.19
Test2 - with plist (i.e. with only patch 1/4 as is)
===================================================
Iterations=1000
Latency (s) min max avg stddev
26.87 28.18 27.30 0.18
Test3 - with plist but all SHED_OTHER registered
with the same priority (MAX_RT_PRIO)
(i.e. with modified patch 1/4, patch not yet posted here)
=========================================================
Iterations=1000
Latency (s) min max avg stddev
26.74 27.84 27.16 0.18
--
Pierre
next prev parent reply other threads:[~2007-01-16 8:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 16:15 [PATCH 2.6.20-rc4 0/4] futexes functionalities and improvements Pierre Peiffer
2007-01-11 17:47 ` Ulrich Drepper
[not found] ` <20070111134615.34902742.akpm@osdl.org>
2007-01-12 7:53 ` Pierre Peiffer
2007-01-12 7:58 ` Ingo Molnar
2007-01-16 8:34 ` Pierre Peiffer [this message]
2007-01-16 9:44 ` Ingo Molnar
2007-01-16 15:14 ` Ulrich Drepper
2007-01-16 15:40 ` Ingo Molnar
2007-01-16 17:46 ` Ulrich Drepper
2007-01-16 17:50 ` Ingo Molnar
2007-01-17 7:50 ` Pierre Peiffer
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=45AC8E2A.3060708@bull.net \
--to=pierre.peiffer@bull.net \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.