From: Jie Chen <chen@jlab.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Simon Holm Th??gersen <odie@cs.aau.dk>,
Eric Dumazet <dada1@cosmosbay.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: Possible bug from kernel 2.6.22 and above, 2.6.24-rc4
Date: Wed, 05 Dec 2007 17:16:51 -0500 [thread overview]
Message-ID: <47572353.4040606@jlab.org> (raw)
In-Reply-To: <20071205210222.GA30089@elte.hu>
Ingo Molnar wrote:
> * Jie Chen <chen@jlab.org> wrote:
>
>>> sorry to be dense, but could you give me instructions how i could
>>> remove the affinity mask and test the "barrier overhead" myself? I
>>> have built "pthread_sync" and it outputs numbers for me - which one
>>> would be the barrier overhead: Reference_time_1 ?
>> To disable affinity, do configure --enable-public-release
>> --disable-thread_affinity. You should see barrier overhead like the
>> following: Computing BARRIER time
>>
>> Sample_size Average Min Max S.D. Outliers
>> 20 19.486162 19.482250 19.491400 0.002740 0
>>
>> BARRIER time = 19.486162 microseconds +/- 0.005371
>> BARRIER overhead = 8.996257 microseconds +/- 0.006575
>
> ok, i did that and rebuilt. I also did "make check" and got
> src/pthread_sync which i can run. The only thing i'm missing, if i run
> src/pthread_sync, it outputs "PARALLEL time":
>
> PARALLEL time = 22.486103 microseconds +/- 3.944821
> PARALLEL overhead = 10.638658 microseconds +/- 10.854154
>
> not "BARRIER time". I've re-read the discussion and found no hint about
> how to build and run a barrier test. Either i missed it or it's so
> obvious to you that you didnt mention it :-)
>
> Ingo
Hi, Ingo:
Did you do configure --enable-public-release? My qmt is for qcd
calculation (one type of physics code). Without the above flag one can
only test PARALLEL overhead. Actually the PARALLEL benchmark has the
same behavior as the BARRIER. Thanks.
###############################################
Jie Chen
Scientific Computing Group
Thomas Jefferson National Accelerator Facility
12000, Jefferson Ave.
Newport News, VA 23606
(757)269-5046 (office) (757)269-6248 (fax)
chen@jlab.org
###############################################
next prev parent reply other threads:[~2007-12-05 22:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 20:34 Possible bug from kernel 2.6.22 and above Jie Chen
2007-11-21 22:14 ` Eric Dumazet
2007-11-22 1:52 ` Jie Chen
2007-11-22 2:32 ` Simon Holm Thøgersen
2007-11-22 2:58 ` Jie Chen
2007-11-22 20:19 ` Matt Mackall
2007-12-04 13:17 ` Possible bug from kernel 2.6.22 and above, 2.6.24-rc4 Ingo Molnar
2007-12-04 15:41 ` Jie Chen
2007-12-05 15:29 ` Jie Chen
2007-12-05 15:40 ` Ingo Molnar
2007-12-05 16:16 ` Eric Dumazet
2007-12-05 16:25 ` Ingo Molnar
2007-12-05 16:29 ` Eric Dumazet
2007-12-05 16:22 ` Jie Chen
2007-12-05 16:47 ` Ingo Molnar
2007-12-05 17:47 ` Jie Chen
2007-12-05 20:03 ` Ingo Molnar
2007-12-05 20:23 ` Jie Chen
2007-12-05 20:46 ` Ingo Molnar
2007-12-05 20:52 ` Jie Chen
2007-12-05 21:02 ` Ingo Molnar
2007-12-05 22:16 ` Jie Chen [this message]
2007-12-06 10:43 ` Ingo Molnar
2007-12-06 16:29 ` Jie Chen
2007-12-10 10:59 ` Ingo Molnar
2007-12-10 20:04 ` Jie Chen
2007-12-11 10:51 ` Ingo Molnar
2007-12-11 15:28 ` Jie Chen
2007-12-11 15:52 ` Ingo Molnar
2007-12-11 16:39 ` Jie Chen
2007-12-11 21:23 ` Ingo Molnar
2007-12-11 22:11 ` Jie Chen
2007-12-12 12:49 ` Peter Zijlstra
2007-12-05 20:36 ` Possible bug from kernel 2.6.22 and above Peter Zijlstra
2007-12-05 20:53 ` Jie Chen
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=47572353.4040606@jlab.org \
--to=chen@jlab.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=odie@cs.aau.dk \
/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).