public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Andrew Morton <akpm@osdl.org>
Cc: warudkar@vsnl.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4-mm1 - kswap hogs cpu OO takes ages to start!
Date: Thu, 28 Aug 2003 12:11:43 +1000	[thread overview]
Message-ID: <200308281211.43945.kernel@kolivas.org> (raw)
In-Reply-To: <20030827125310.15ebf8f9.akpm@osdl.org>

On Thu, 28 Aug 2003 05:53, Andrew Morton wrote:
> Con Kolivas <kernel@kolivas.org> wrote:
> > On Thu, 28 Aug 2003 07:38, warudkar@vsnl.net wrote:
> > > Trying out 2.6.0-test4-mm1. Inside KDE, I start OpenOffice.org,
> > > Rational Rose and Konsole at a time. All of these take extremely long
> > > time to startup. (approx > 5 minutes). Kswapd hogs the CPU all the
> > > time. X becomes unusable till all of them startup, although I can
> > > telnet and run top. Same thing run under 2.4.18 starts up in 3 minutes,
> > > X stays usable and kswapd never take more than 2% CPU.
> >
> > Yes I can reproduce this with a memory heavy load as well on low memory
> > (linking at the end of a big kernel compile is standard problem).
>
> It could be that recent changes to page reclaim which improve I/O
> scheduling have exacerbated this.
>
> Does this make a difference?

Tried it. No change. 

kswapd0 can hit 90% cpu at times unless the swappiness is increased.

Con


  reply	other threads:[~2003-08-28  2:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 21:38 2.6.0-test4-mm1 - kswap hogs cpu OO takes ages to start! warudkar
2003-08-27 11:18 ` William Lee Irwin III
2003-08-27 11:30 ` William Lee Irwin III
2003-08-27 11:37 ` Con Kolivas
2003-08-27 19:53   ` Andrew Morton
2003-08-28  2:11     ` Con Kolivas [this message]
2003-08-31 16:06       ` Rik van Riel
2003-08-28  3:23     ` Tariq Firoz
2003-08-27 12:17 ` Jose Luis Domingo Lopez

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=200308281211.43945.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=warudkar@vsnl.net \
    /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