linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "ZINKEVICIUS,MATT (HP-Loveland,ex1)" <matt_zinkevicius@hp.com>
To: 'Jens Axboe' <axboe@suse.de>, linux-mm@kvack.org
Subject: RE: 2.4.6pre3: kswapd dominating CPU
Date: Mon, 25 Jun 2001 15:02:02 -0700	[thread overview]
Message-ID: <F341E03C8ED6D311805E00902761278C07EFA68B@xfc04.fc.hp.com> (raw)

> 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

We tried your block-highmem patch for 2.4.6pre1 (the 2.4.5 one you suggested
didn't patch cleanly). Sadly the kernel is unbootable (stops at
"uncompressing kernel..."). If you give as an updated patch for 2.4.6pre3 we
will be happy to try it!

> Dunno what I/O controller you used...

Qlogic fibre channel card (kernel's qlogicfc driver)

--Matt

PS: We also have tried Andrea's 2.4.6pre3aa2 patch. kswapd/kupdated still
runs but at much less CPU utilization (30%-70%) but for much longer periods
having an overall worsening effect. It also breaks fsync which in turn
breaks lots of things (lilo, etc).
--
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/

             reply	other threads:[~2001-06-25 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-25 22:02 ZINKEVICIUS,MATT (HP-Loveland,ex1) [this message]
2001-06-25 22:05 ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
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

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=F341E03C8ED6D311805E00902761278C07EFA68B@xfc04.fc.hp.com \
    --to=matt_zinkevicius@hp.com \
    --cc=axboe@suse.de \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox