linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "ZINKEVICIUS,MATT (HP-Loveland,ex1)" <matt_zinkevicius@hp.com>
Cc: "'linux-mm@kvack.org'" <linux-mm@kvack.org>
Subject: Re: 2.4.6pre3: kswapd dominating CPU
Date: Mon, 25 Jun 2001 20:34:00 +0200	[thread overview]
Message-ID: <20010625203400.D3327@suse.de> (raw)
In-Reply-To: <F341E03C8ED6D311805E00902761278C07EFA675@xfc04.fc.hp.com>; from matt_zinkevicius@hp.com on Mon, Jun 18, 2001 at 05:12:44PM -0700

On Mon, Jun 18 2001, ZINKEVICIUS,MATT (HP-Loveland,ex1) wrote:
> [...] This seems related
> to whether we enable highmem in the kernel, as this problem only appears
> when highmem is set to 4GB or 64GB. Any hints?
> 
> Server specs:
> HP LT6000r server
> 4 x 700Mhz P3Xeons
> 4GB RAM
> 1GB swap partition
> 2.4.6pre3 kernel

WIth a machine spec'ed like that, you might want to try with the
zero-bounce patches for highmem machines. Running out of memory and
still requiring low mem bounce buffers can get ugly -- the patches won't
solve any vm issues, but they should solve the problem for you (and
boost your specsfs performance a good deal).

Haven't had time to update to 2.4.6-pre3 yet, if these don't apply let
me know:

*.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.5/block-highmem-all-4.bz2

Dunno what I/O controller you used...

-- 
Jens Axboe

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  parent reply	other threads:[~2001-06-25 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-19  0:12 ZINKEVICIUS,MATT (HP-Loveland,ex1)
2001-06-19 19:05 ` Rik van Riel
2001-06-25 18:34 ` Jens Axboe [this message]
2001-06-25 22:02 ZINKEVICIUS,MATT (HP-Loveland,ex1)
2001-06-25 22:05 ` Jens Axboe

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=20010625203400.D3327@suse.de \
    --to=axboe@suse.de \
    --cc=linux-mm@kvack.org \
    --cc=matt_zinkevicius@hp.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