From: Pedro Gonnet <gonnet@maths.ox.ac.uk>
To: linux-rt-users@vger.kernel.org
Subject: Question regarding pthread_cond_wait/pthread_cond_signal latencies
Date: Fri, 20 May 2011 11:08:36 +0100 [thread overview]
Message-ID: <1305886116.10494.30.camel@laika> (raw)
Hi guys,
I'm currently working on a shared-memory parallel Molecular Dynamics
simulation library (http://mdcore.sourceforge.net/) geared towards
multi-core systems.
The library uses pthreads (plus some OpenMP for some simple loops) and
uses pthread_cond_wait and pthread_cond_signal to coordinate a group of
worker threads.
I've been profiling the library on different machines and kernels and
have noticed that in many cases there are significant (several ms,
measured with Intel's Vtune-thing) lags between calls to
pthread_cond_signal and the waiting thread actually getting back to
work.
I've tried the Ubuntu -rt and -preempt kernels, and the whole simulation
runs twice as slowly, despite following the advice given here:
https://rt.wiki.kernel.org/index.php/HOWTO:_Build_an_RT-application
My question is the following: which kernel (or set of configuration
options) will minimize these latencies? And if linux-rt is the answer,
in what ways do I have to be careful when porting the simulation for
this kernel?
Cheers and thanks,
Pedro
next reply other threads:[~2011-05-20 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 10:08 Pedro Gonnet [this message]
2011-05-21 20:48 ` Question regarding pthread_cond_wait/pthread_cond_signal latencies Mark Hounschell
2011-05-21 20:51 ` Pedro Gonnet
2011-05-21 21:40 ` Rolando Martins
2011-05-22 0:44 ` Peter W. Morreale
2011-05-22 11:34 ` Pedro Gonnet
2011-05-22 13:51 ` Peter W. Morreale
2011-05-22 18:37 ` Robert Schwebel
-- strict thread matches above, loose matches on Subject: below --
2011-05-20 11:15 Pedro Gonnet
2011-05-22 14:53 ` Armin Steinhoff
2011-05-22 15:18 ` Armin Steinhoff
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=1305886116.10494.30.camel@laika \
--to=gonnet@maths.ox.ac.uk \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).