From: Thomas Hood <jdthood@mail.com>
To: Jeff Chua <jchua@fedex.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Stephan von Krawczynski <skraw@ithnet.com>
Subject: Re: 2.4.18-pre7 slow ... apm problem
Date: Mon, 28 Jan 2002 15:28:27 -0500 [thread overview]
Message-ID: <1012249707.4807.123.camel@thanatos> (raw)
In-Reply-To: <Pine.LNX.4.44.0201290351520.7623-100000@boston.corp.fedex.com>
In-Reply-To: <Pine.LNX.4.44.0201290351520.7623-100000@boston.corp.fedex.com>
On Mon, 2002-01-28 at 15:11, Jeff Chua wrote:
> Sorry, just got off a long flight from San Diego to Singapore. Anyway,
> slow ... means that even without vmware, if I just hit return, the lines
> would scroll for about every 10 lines and there'll be a litte pause (<0.3
> sec). With pre6, there's no such behavior, and if CONFIG_APM_CPU_IDLE is
> not set, the "pause" goes away.
Suggestion: Try setting the idle_threshold to a higher value,
e.g., 98. (The default value is 95.)
Question to all: Would it be a good idea to de-idle the CPU
inside interrupt handlers?
> "host" system is linux. "guest" system is linux (actually, I tried with NT
> as well, same problem).
>
> The sympton is when I try to ping the "host" from vmware's "guest" system,
> the first response came back to the guest's console. Then if I don't type
> anything or don't move the mouse on the guest's console, I won't see any
> further response on the guest's linux console. Even with a lot of mouse
> movement or pressing the keys, the response is still very slow with "ping".
> If I ping from the "host" linux console to the "guest" linux system,
> responses came back, and does not hang. I'll double check this last point.
> Got to recompile the kernel again.
Try disabling APM cpu idling (set apm idle_threshold to 100) in the
_guest_ OS. (Leave it enabled in the host OS.) Tell us what happens.
Also try disabling APM cpu idling (set apm idle_threshold to 100) in
the _host_ OS. (Leave it enabled in the guest OS.) Tell us what
happens.
I repeat: You do not need to recompile the kernel to enable/disable
APM cpu idle: to disable it simply set idle_threshold to 100.
next prev parent reply other threads:[~2002-01-28 22:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 0:15 2.4.18-pre7 slow ... apm problem Thomas Hood
2002-01-28 0:32 ` Alan Cox
2002-01-28 2:37 ` Thomas Hood
2002-01-28 10:14 ` Alan Cox
2002-01-28 11:25 ` Thomas Hood
2002-01-28 13:03 ` Stephan von Krawczynski
2002-01-28 13:18 ` Alan Cox
2002-01-28 16:19 ` Thomas Hood
2002-01-28 3:22 ` Thomas Hood
2002-01-28 20:11 ` Jeff Chua
2002-01-28 20:28 ` Thomas Hood [this message]
2002-01-28 22:20 ` Alan Cox
2002-01-29 12:36 ` Jeff Chua
2002-01-30 1:12 ` Thomas Hood
2002-01-30 9:22 ` Jeff Chua
2002-01-28 21:14 ` Thomas Hood
2002-01-28 21:17 ` Jeff Chua
2002-01-28 23:09 ` Stephan von Krawczynski
2002-01-29 13:01 ` Jeff Chua
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 18:53 Petr Vandrovec
2002-01-29 22:47 ` Stephan von Krawczynski
2002-01-30 0:44 ` Jeff Chua
2002-01-30 5:50 ` Stephen Rothwell
2002-01-30 9:27 ` Jeff Chua
2002-02-01 13:20 ` Jeff Chua
2002-01-28 23:22 Petr Vandrovec
2002-01-27 10:08 Jeff Chua
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=1012249707.4807.123.camel@thanatos \
--to=jdthood@mail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jchua@fedex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=skraw@ithnet.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 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.