public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tariq Firoz" <tariq_firoz@infosys.com>
To: "Andrew Morton" <akpm@osdl.org>, "Con Kolivas" <kernel@kolivas.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 08:53:04 +0530	[thread overview]
Message-ID: <021901c36d13$b174bd90$edbccac6@itlpc5228> (raw)
In-Reply-To: 20030827125310.15ebf8f9.akpm@osdl.org

I faced a similar problem with 2.6.0-test4-mm2 while using unstable kde
3.1.9x(?)
In fact I was not able to do anything and my system became unresponsive,
with kswapd0
hogging 60% CPU. Later X got killed ... I did not face such a situation in
any of the previous
releases (I have been using 2.5 since 2.5.70 )

[ I have 256 MB RAM and 256 SWAP with P4 2.0 GHz]

Tariq Firoz


----- Original Message -----
From: "Andrew Morton" <akpm@osdl.org>
To: "Con Kolivas" <kernel@kolivas.org>
Cc: <warudkar@vsnl.net>; <linux-kernel@vger.kernel.org>
Sent: Thursday, August 28, 2003 1:23 AM
Subject: Re: 2.6.0-test4-mm1 - kswap hogs cpu OO takes ages to start!


> 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?
>
> diff -puN mm/vmscan.c~a mm/vmscan.c
> --- 25/mm/vmscan.c~a Wed Aug 27 12:51:36 2003
> +++ 25-akpm/mm/vmscan.c Wed Aug 27 12:51:48 2003
> @@ -360,8 +360,6 @@ shrink_list(struct list_head *page_list,
>   * See swapfile.c:page_queue_congested().
>   */
>   if (PageDirty(page)) {
> - if (referenced)
> - goto keep_locked;
>   if (!is_page_cache_freeable(page))
>   goto keep_locked;
>   if (!mapping)
>
> _
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


  parent reply	other threads:[~2003-08-28  3:17 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
2003-08-31 16:06       ` Rik van Riel
2003-08-28  3:23     ` Tariq Firoz [this message]
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='021901c36d13$b174bd90$edbccac6@itlpc5228' \
    --to=tariq_firoz@infosys.com \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.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