From: Brian Tinsley <btinsley@emageon.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20, .text.lock.swap cpu usage? (ibm x440)
Date: Thu, 09 Jan 2003 23:45:25 -0600 [thread overview]
Message-ID: <3E1E5DF5.70808@emageon.com> (raw)
In-Reply-To: 20030110052439.GL23814@holomorphy.com
>
>
>Okay, can you try with either 2.4.x-aa or 2.5.x-CURRENT?
>
Yes, I *just* booted a machine with 2.4.20-aa1 in our lab. I was having
problems compiling the Linux Virtual Server code, but it's fixed now.
>I'm suspecting either bh problems or lowpte problems.
>
>Also, could you monitor your load with the scripts I posted?
>
>
Yes, they are already uploaded to a customer site and ready to go. I
need to flex the -aa1 kernel a bit before I load it there as well.
Thanks!
next prev parent reply other threads:[~2003-01-10 5:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 3:17 2.4.20, .text.lock.swap cpu usage? (ibm x440) Brian Tinsley
2003-01-10 3:29 ` William Lee Irwin III
2003-01-10 3:42 ` Brian Tinsley
2003-01-10 3:54 ` William Lee Irwin III
2003-01-10 4:08 ` Brian Tinsley
2003-01-10 4:19 ` William Lee Irwin III
2003-01-10 4:50 ` Brian Tinsley
2003-01-10 5:17 ` Martin J. Bligh
2003-01-10 5:24 ` William Lee Irwin III
2003-01-10 5:45 ` Brian Tinsley [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 23:35 Chris Wood
2003-01-06 23:50 ` William Lee Irwin III
2003-01-06 23:52 ` Andrew Morton
2003-01-09 17:17 ` Chris Wood
2003-01-09 20:18 ` Andrew Morton
2003-01-10 0:25 ` William Lee Irwin III
2003-01-10 0:44 ` Brian Tinsley
2003-01-10 0:55 ` William Lee Irwin III
2003-01-10 20:42 ` Chris Wood
2003-01-09 2:20 ` James Cleverdon
2003-01-09 2:57 ` William Lee Irwin III
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=3E1E5DF5.70808@emageon.com \
--to=btinsley@emageon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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