From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: Ankita Garg <ankita@in.ibm.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Gregory Haskins <ghaskins@novell.com>,
Ingo Molnar <mingo@elte.hu>,
Dinakar Guniguntala <dino@in.ibm.com>,
Darren Hart <dvhltc@us.ibm.com>,
Mike Kravetz <kravetz@us.ibm.com>
Subject: Re: High 50us+ latencies in the process signal handling path
Date: Fri, 19 Oct 2007 14:43:44 +0200 [thread overview]
Message-ID: <4718A680.5000501@stud.feec.vutbr.cz> (raw)
In-Reply-To: <20071018124827.GA22282@in.ibm.com>
Ankita Garg wrote:
> Hi,
>
> There is a testcase called 'pthread_kill_latency' under the rt-test suite
> on the the RT Wiki:
>
> http://www.kernel.org/pub/linux/kernel/people/dvhart/realtime/tests/rt-test-0.3.tar.bz2
>
> Description of the testcase:
>
> The test measures the latency involved in sending a signal to a thread
> using pthread_kill. Two threads are created, receiver thread (thread1)
> and sender thread (thread2). Before sending the signal, it waits for
> thread1 to initialize (thread1 waits by calling sigwait), notes the time and
> send pthread_kill signal to thread1. thread1 notes the time it receives the
> signal. The maximum and the minimum latency is reported. This is repeated
> about 10000 times.
>
I'm looking at the source. The receiver thread runs with realtime
priority (it's created with create_fifo_thread), but the sender thread
(thread2) doesn't (create_other_thread). The sender does:
/* Record the time just before sending the signal */
begin = rt_gettime();
/**** The sender can get preempted by anything right here ! ****/
if ((ret = pthread_kill(PTHREADOF(target_thread), SIGNALNUMBER))) {
printf("pthread_kill returned %d\n", ret);
}
Can this explain it?
Michal
next prev parent reply other threads:[~2007-10-19 12:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 12:48 High 50us+ latencies in the process signal handling path Ankita Garg
2007-10-18 12:52 ` David Miller
2007-10-18 13:26 ` Ankita Garg
2007-10-18 13:38 ` Steven Rostedt
2007-10-19 11:11 ` Ankita Garg
2007-10-18 15:36 ` Luis Claudio R. Goncalves
2007-10-19 6:28 ` Ankita Garg
2007-10-18 13:32 ` Steven Rostedt
2007-10-19 12:43 ` Michal Schmidt [this message]
2007-10-19 12:53 ` Steven Rostedt
2007-10-19 14:20 ` Sripathi Kodi
2007-10-25 1:24 ` Steven Rostedt
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=4718A680.5000501@stud.feec.vutbr.cz \
--to=xschmi00@stud.feec.vutbr.cz \
--cc=ankita@in.ibm.com \
--cc=dino@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=ghaskins@novell.com \
--cc=kravetz@us.ibm.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 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.