From: Rusty Russell <rusty@rustcorp.com.au>
To: Matt Mackall <mpm@selenic.com>
Cc: Ingo Molnar <mingo@elte.hu>,
akpm@linux-foundation.org, Linux-kernel@vger.kernel.org
Subject: Re: Interesting interaction between lguest and CFS
Date: Tue, 05 Jun 2007 10:18:54 +1000 [thread overview]
Message-ID: <1181002734.25878.56.camel@localhost.localdomain> (raw)
In-Reply-To: <20070604173710.GR11166@waste.org>
On Mon, 2007-06-04 at 12:37 -0500, Matt Mackall wrote:
> With 2.6.22-rc3-mm1, I've got a long-running video transcoding going
> on. In other windows, I'm compiling, reading email, etc. with no
> noticeable problems.
>
> If I fire up lguest and leave it sitting at a shell prompt for a
> couple moments, when I return to type something at the prompt, it can
> take 2-3 seconds for my input to echo. Once it starts responding,
> typing latency disappears. Suspend the other app and the latency
> disappears.
This sounds like the waker process (nice 19) not getting a chance to
run. You can hack around it for the moment by changing "nice(19)" in
Documentation/lguest/lguest.c to something less aggressive.
The real solution is to switch to an fd. Fortunately, I have just such
a patch. I am shuffling it forward in my queue now, and will send when
testing is complete...
Thanks!
Rusty.
next prev parent reply other threads:[~2007-06-05 0:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 17:37 Interesting interaction between lguest and CFS 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
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 [this message]
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=1181002734.25878.56.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=Linux-kernel@vger.kernel.org \
--cc=akpm@linux-foundation.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
/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