From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Matt Mackall" <mpm@selenic.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Rusty Russell" <rusty@rustcorp.com.au>,
akpm@linux-foundation.org, Linux-kernel@vger.kernel.org
Subject: Re: Interesting interaction between lguest and CFS
Date: Tue, 5 Jun 2007 17:14:12 +0200 [thread overview]
Message-ID: <b647ffbd0706050814u1e145b82qdb344d475d9ffe93@mail.gmail.com> (raw)
In-Reply-To: <20070605140342.GR11115@waste.org>
On 05/06/07, Matt Mackall <mpm@selenic.com> wrote:
> > [...]
> > Click into the lguest window and trigger the delay.
>
> I did:
>
> while true; do sleep 1; cat /proc/sched_debug > sched_debug.txt; done
>
> and got this, hopefully inside the window:
>
> Sched Debug Version: v0.02
> now at 257428593818894 nsecs
>
> cpu: 0
> .nr_running : 3
> .raw_weighted_load : 2063
> .nr_switches : 242830075
> .nr_load_updates : 30172063
> .nr_uninterruptible : 0
> .jiffies : 64282148
> .next_balance : 0
> .curr->pid : 27182
> .clock : 125650217819008823
> .prev_clock_raw : 257428516403535
The delta (clock - prev_clock_raw) looks insane.
The current time (which doesn't depend on rq_clock() --> sched_clock() is
" now at 257428593818894 nsecs " (right at the beginning of the output).
'prev_clock_raw' is updated any time rq_clock() is called - basically
upon any scheduling operation (e.g. enqueue/dequeue)
now - prev_clock_raw == 257428593818894 - 257428516403535 == ~ 80 ms.
while 'clock' reports something crazy.. that would explain why there
wes a huge "block_max" reported earlier.. I guess, sched_clock() is
tsc-based in your case?
Any way to get it switched to jiffies-based one and repeat the test?
--
Best regards,
Dmitry Adamushko
next prev parent reply other threads:[~2007-06-05 15:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 17:37 Matt Mackall
2007-06-04 17:54 ` Ingo Molnar
2007-06-04 18:41 ` Matt Mackall
2007-06-05 7:19 ` Ingo Molnar
2007-06-05 14:03 ` Matt Mackall
2007-06-05 15:14 ` Dmitry Adamushko [this message]
2007-06-05 15:41 ` Dmitry Adamushko
2007-06-05 19:50 ` Ingo Molnar
2007-06-06 20:23 ` Matt Mackall
2007-06-08 9:34 ` Ingo Molnar
2007-06-08 10:18 ` Ingo Molnar
2007-06-04 18:11 ` Ingo Molnar
2007-06-04 18:42 ` Matt Mackall
2007-06-04 19:12 ` Ingo Molnar
2007-06-04 19:27 ` Matt Mackall
2007-06-04 19:40 ` Ingo Molnar
2007-06-04 19:59 ` Matt Mackall
2007-06-04 20:13 ` Ingo Molnar
2007-06-04 20:20 ` Ingo Molnar
2007-06-04 20:15 ` James Morris
2007-06-04 20:24 ` Ingo Molnar
2007-06-04 22:58 ` Olof Johansson
2007-06-05 1:02 ` Rusty Russell
2007-06-05 1:24 ` Stephen Rothwell
2007-06-05 2:23 ` Olof Johansson
2007-06-05 0:18 ` Rusty Russell
2007-06-05 2:31 ` Rusty Russell
2007-06-05 4:18 ` Matt Mackall
2007-06-05 4:37 ` Rusty Russell
2007-06-05 13:49 ` Matt Mackall
2007-06-05 19:38 ` Ingo Molnar
2007-06-05 10:43 ` Ingo Molnar
2007-06-05 19:08 ` Ingo Molnar
2007-06-06 20:19 ` Matt Mackall
2007-06-05 2:34 ` Matt Mackall
2007-06-05 7:10 ` Ingo Molnar
2007-06-05 9:23 ` Ingo Molnar
2007-06-05 14:06 ` Matt Mackall
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=b647ffbd0706050814u1e145b82qdb344d475d9ffe93@mail.gmail.com \
--to=dmitry.adamushko@gmail.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=akpm@linux-foundation.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®