From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
"Arjan van de Ven" <arjan@linux.intel.com>
Subject: Re: printk timestamps jumping back and forth in 2.6.25-rc.
Date: Sat, 1 Mar 2008 03:42:17 +0300 [thread overview]
Message-ID: <f19298770802291642v56a8a50ve5c7c88de53513f4@mail.gmail.com> (raw)
In-Reply-To: <20080229194547.GC21249@elte.hu>
On Fri, Feb 29, 2008 at 10:45 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Alexey Zaytsev <alexey.zaytsev@gmail.com> wrote:
>
>
>
> > On Thu, Feb 28, 2008 at 11:16 PM, Ingo Molnar <mingo@elte.hu> wrote:
> > >
> > > * Ingo Molnar <mingo@elte.hu> wrote:
> > >
> > > > > Anything else I can do?
> > > >
> > > > yes, please test the patch below - does it fix the problem?
> >
> > The patch worked well, thanks
> >
> > I still observe some uneven mouse behaviour during compilations (linux
> > kernel, make -j 6), like, when I slowly move the mouse, it would stop
> > for a split of a second every few seconds (the intervals are not
> > equal). On 2.6.23/24 it works very smooth. Of course, I can't say that
> > the scheduler is to be blamed. It was only my assumption because I
> > thought I might be confused by the non-monotinic time, which I see is
> > not the case. Any ideas, how to debug this?
>
> could you try latencytop, what does it say, what type of scheduler (and
> other) delays are there?
>
I'm not sure I fully understand how to use this tool.
There are clearly two possible options to the utility,
--unknown and -d, but I still have no idea what they do..
Does the latencytop-0.3 actually work? I my case the upper half of the
window is always empty. The lower half shows always one line, like
Scheduler: waiting for cpu \t \t \t \t $some_val $some_val
The two values are always identical.
In the 2.6.24 case, the values for Xorg are always around 20 ms
when a make -j 6 is runig in parallel. For the 2.6.25 the
values jump from 100 ms to over 1000 ms.
Later I mounted a tmpfs and run the compilation (from root) there
(swap turned off). This time the Xorg latency was usually less then
30 ms, but the gnome-terminal (running from an other user) was not
that lucky with latencies around 500-1000 ms. Now I ran the same compilation
from user, and the latencies came back to what I observed before, with
gnome-terminal being about 30-50 and Xorg jumping from 100 to now
over 2000. The latencytop and some daemons runnig as different users
also had comparable latencyes.
Yes, fair group scheduler enabled, the config can be seen here:
http://romomatic.osuosl.org/share/xl0/config-2.6.25-rc3
I"ll now recompile with fair group scheduler disabled, just to be sure.
next prev parent reply other threads:[~2008-03-01 0:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 14:26 Alexey Zaytsev
2008-02-28 19:21 ` David Miller
2008-02-28 20:13 ` Ingo Molnar
2008-02-28 20:16 ` Ingo Molnar
2008-02-28 21:24 ` Alexey Zaytsev
2008-02-29 19:45 ` Ingo Molnar
2008-03-01 0:42 ` Alexey Zaytsev [this message]
2008-03-01 0:59 ` Alexey Zaytsev
2008-03-03 10:45 ` Ingo Molnar
2008-03-03 22:16 ` Alexey Zaytsev
2008-03-04 12:44 ` Ingo Molnar
2008-02-29 11:11 ` Paul Mackerras
2008-02-29 18:42 ` David Miller
2008-02-29 19:44 ` Ingo Molnar
2008-03-21 18:55 ` Alexey Zaytsev
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=f19298770802291642v56a8a50ve5c7c88de53513f4@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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®