From: Kevin Winchester <kjwinchester@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Frans Pop <elendil@planet.nl>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mike Galbraith <efault@gmx.de>,
Richard Jonsson <richie@coderworld.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [git pull] scheduler changes for v2.6.26
Date: Tue, 22 Apr 2008 06:41:47 -0300 [thread overview]
Message-ID: <480DB2DB.9040908@gmail.com> (raw)
In-Reply-To: <20080421194359.GD8770@elte.hu>
Ingo Molnar wrote:
> * Frans Pop <elendil@planet.nl> wrote:
>
>>> It would be nice if you could try sched-devel/latest because it has
>>> an improved ftrace "sched_switch" tracer where you can generate much
>>> longer traces of this incident. Try the new /debug/trace_entries
>>> runtime tunable.
>> I'll try to get the trace and will reply on the private thread we had.
>> I may need additional instructions though.
>
> you could also reply to this thread if you dont mind, so that others can
> chime in too.
>
> the 700-800 msecs of delays you see are very "brutal" so there must be
> something fundamentally wrong going on here.
>
> Could you first check (under sched-devel/latest) the quality of your
> sched-clock, via running this script:
>
> http://people.redhat.com/mingo/cfs-scheduler/tools/watch-rq-clock.sh
>
> if you run it, it should output ~1000 msecs periods every second:
>
> europe:~> watch-rq-clock.sh
> 1002.115042
> 1005.509851
> 1004.187275
> 1004.409980
> 1004.430264
> 1004.445508
>
> if it's way too 'slow', say it only 100 msecs per second, then the
> scheduler clock is mis-measuring time and what the scheduler thinks to
> be a 40 msecs delay might become a 400 msecs delay.
>
Is this supposed to be true for everyone?
kevin@alekhine:~/linux$ uname -a
Linux alekhine 2.6.25-02519-g3925e6f #10 PREEMPT Sat Apr 19 12:36:49 ADT 2008 x86_64 GNU/Linux
kevin@alekhine:~/linux$ ./watch-rq-clock.sh
89.986517
81.033471
76.942776
90.986318
75.988551
85.987089
74.988696
85.987078
73.988858
88.986641
68.989600
kevin@alekhine:~/linux$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 31
model name : AMD Athlon(tm) 64 Processor 3000+
stepping : 0
cpu MHz : 1000.000
cache size : 512 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow
rep_good lahf_lm
bogomips : 2006.79
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp
Does that mean anything? Is there any other testing I should perform?
--
Kevin Winchester
next prev parent reply other threads:[~2008-04-22 10:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 18:13 [git pull] scheduler changes for v2.6.26 Ingo Molnar
2008-04-19 18:47 ` Guillaume Chazarain
2008-04-19 18:49 ` Ingo Molnar
2008-04-19 18:54 ` Peter Zijlstra
2008-04-19 19:47 ` Frans Pop
2008-04-21 12:39 ` Ingo Molnar
2008-04-21 16:31 ` Frans Pop
2008-04-21 19:43 ` Ingo Molnar
2008-04-22 8:51 ` Mike Galbraith
2008-04-22 8:59 ` Ingo Molnar
2008-04-22 9:59 ` Peter Zijlstra
2008-04-22 12:25 ` Mike Galbraith
2008-04-23 8:11 ` Mike Galbraith
2008-04-23 10:30 ` Mike Galbraith
2008-04-23 11:21 ` Peter Zijlstra
2008-04-23 13:27 ` Mike Galbraith
2008-04-22 9:41 ` Kevin Winchester [this message]
2008-04-22 10:49 ` David Miller
2008-04-22 11:10 ` Peter Zijlstra
2008-04-23 9:36 ` Frans Pop
2008-04-23 9:42 ` Peter Zijlstra
2008-04-23 9:46 ` Ingo Molnar
2008-04-23 13:36 ` Frans Pop
2008-04-29 12:29 ` Ingo Molnar
2008-04-29 15:28 ` Steven Rostedt
2008-04-23 16:23 ` Frans Pop
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=480DB2DB.9040908@gmail.com \
--to=kjwinchester@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=richie@coderworld.net \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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.