From: Arun Sharma <asharma@fb.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-perf-users@vger.kernel.org, acme@ghostprotocols.net,
mingo@elte.hu, Stephane Eranian <eranian@google.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Vagin <avagin@gmail.com>
Subject: Re: Profiling sleep times?
Date: Thu, 6 Oct 2011 14:56:39 -0700 [thread overview]
Message-ID: <4E8E2417.2000903@fb.com> (raw)
In-Reply-To: <1317717291.25926.13.camel@twins>
On 10/4/11 1:34 AM, Peter Zijlstra wrote:
>> # cat foo.c
>> #include<unistd.h>
>> #include<time.h>
>> #include<sys/select.h>
>>
>> main()
>> {
>> struct timespec ts1;
>> struct timeval tv1;
>> int i;
>>
>>
>> for (i = 0; i< 1000; i++) {
>> ts1.tv_sec = 0;
>> ts1.tv_nsec = 1000000;
>> nanosleep(&ts1, NULL);
>>
>> tv1.tv_sec = 0;
>> tv1.tv_usec = 4000;
>> select(0, NULL, NULL, NULL,&tv1);
>> }
>> }
>>
> Would you per-chance be suffering from this:
>
> http://lkml.kernel.org/r/1317052535-1765247-2-git-send-email-avagin@openvz.org
>
Thanks for the pointer. Yes - Andrew's patches help. But looks like we
need more user space plumbing like Frederic noted.
perf record -ge sched:sched_stat_sleep -- ./foo
doesn't quite work.
perf record -age sched:sched_stat_sleep -- ./foo
gives me:
58.62% foo [unknown] [k] 0
|
--- schedule
|
|--54.99%-- schedule_hrtimeout_range_clock
| schedule_hrtimeout_range
| poll_schedule_timeout
| do_select
| core_sys_select
| sys_select
| system_call_fastpath
|
|--44.81%-- do_nanosleep
| hrtimer_nanosleep
| sys_nanosleep
| system_call_fastpath
--0.20%-- [...]
i.e. select() should be weighted by 4x vs nanosleep() as confirmed via:
perf script | grep comm=foo
foo 15516 [006] 2291.187831: sched_stat_sleep: comm=foo
pid=15516 delay=4054262 [ns]
foo 15516 [006] 2291.187832: sched_stat_sleep: comm=foo
pid=15516 delay=4054262 [ns]
foo 15516 [006] 2291.188895: sched_stat_sleep: comm=foo
pid=15516 delay=1053565 [ns]
foo 15516 [006] 2291.188896: sched_stat_sleep: comm=foo
pid=15516 delay=1053565 [ns]
foo 15516 [006] 2291.188897: sched_stat_sleep: comm=foo
pid=15516 delay=1053565 [ns]
Andrew, are you already working on user space patches?
-Arun
next prev parent reply other threads:[~2011-10-06 21:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 19:38 Profiling sleep times? Arun Sharma
2011-10-03 20:17 ` Peter Zijlstra
2011-10-03 21:53 ` Arun Sharma
2011-10-04 8:34 ` Peter Zijlstra
2011-10-06 21:56 ` Arun Sharma [this message]
2011-10-07 0:05 ` Arun Sharma
2011-10-07 1:30 ` Peter Zijlstra
2011-10-07 5:42 ` avagin
2011-10-07 9:33 ` Peter Zijlstra
2011-10-07 17:58 ` Arun Sharma
2011-10-07 23:16 ` avagin
2011-10-08 1:45 ` avagin
2011-10-10 18:50 ` Arun Sharma
2011-10-12 7:41 ` Ingo Molnar
2011-10-13 5:39 ` Andrew Vagin
2011-10-14 21:19 ` Arun Sharma
2011-10-15 17:00 ` Ingo Molnar
2011-10-15 19:22 ` Peter Zijlstra
2011-10-15 19:29 ` Peter Zijlstra
2011-10-18 1:07 ` Arun Sharma
2011-10-22 10:49 ` Frederic Weisbecker
2011-10-22 16:22 ` Andrew Wagin
2011-10-23 0:27 ` Arun Sharma
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=4E8E2417.2000903@fb.com \
--to=asharma@fb.com \
--cc=acme@ghostprotocols.net \
--cc=avagin@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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.