All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Gregory K. Ruiz-Ade" <gregory@castandcrew.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 instability on bigmem systems?
Date: Fri, 14 Mar 2003 10:31:18 -0800	[thread overview]
Message-ID: <127170000.1047666678@flay> (raw)
In-Reply-To: <200303131627.22572.gregory@castandcrew.com>

> The primary problem:  Whenever any process (or set of processes) initiates 
> intensive disk I/O, the system grinds to a halt, kswapd and kupdated 
> consume upwards of 40% to 60% CPU each, and system load averages can jump 
> upwards of 21.00.  The problem can be replicated with a simple find command 
> ("find / -print" seems to do it nicely).

Well known set of problems. 
2.4 vm sucks on big machines. Run 2.5, 2.4-aa, or UL.

Yes, you can spend a few weeks beating your head against a brick wall 
gathering various bugfixes if you like ... but you'll probably just end
up with a sore head ...

M.


      parent reply	other threads:[~2003-03-14 18:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14  0:27 2.4.20 instability on bigmem systems? Gregory K. Ruiz-Ade
2003-03-14  0:42 ` William Lee Irwin III
2003-03-14  1:45   ` Gregory K. Ruiz-Ade
2003-03-14  1:53     ` William Lee Irwin III
2003-03-14  3:55       ` Gregory K. Ruiz-Ade
2003-03-14  4:13         ` William Lee Irwin III
2003-03-14 17:31           ` Gregory K. Ruiz-Ade
2003-03-14 20:08             ` William Lee Irwin III
2003-03-17  2:15               ` Gregory K. Ruiz-Ade
2003-03-17  2:26                 ` William Lee Irwin III
2003-03-17  4:59                   ` Gregory K. Ruiz-Ade
2003-03-17  5:38                     ` Gregory K. Ruiz-Ade
2003-03-14 18:31 ` Martin J. Bligh [this message]

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=127170000.1047666678@flay \
    --to=mbligh@aracnet.com \
    --cc=gregory@castandcrew.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.