public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nuno Silva <nuno.silva@vgertech.com>
To: Ken Savage <kens1835@shaw.ca>
Cc: linux kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: High CPU load with kswapd and heavy disk I/O
Date: Tue, 12 Aug 2003 20:44:57 +0100	[thread overview]
Message-ID: <3F3943B9.7080700@vgertech.com> (raw)
In-Reply-To: <200308121136.11979.kens1835@shaw.ca>

Hi!

Ken Savage wrote:
> Short version:
> ----------------
> kernels 2.4.17 --> 2.4.21
> Dual Athlon SMP system
> 4GB RAM, 2GB swap
> 3ware RAID, filled with millions of files across thousands of directories.
> reiserfs 3.6
> 
> The following command is guaranteed to lock out the box by activating
> kswapd to >95% CPU, blocking out pings, everything.
> 
>     find /RAID/data/ -type f -mtime +180 | xargs rm
> 

Can you send before, during and after:
cat /proc/meminfo
cat /proc/slabinfo

And maybe:
vmstat 1

Real kernel hackers (not me...) will find that information very usefull ;)

Regards,
Nuno Silva


> Details:
> ----------
> Applying the rmap patch seems to prevent kswapd from hogging the CPU,
> but causes it to freeze up for some other reason.  (The server is remote,
> so I can't view the console.)  Likewise 2.6.0-test* causes freezeups.
> Mind you, the server is under a fair bit of CPU and disk load -- hundreds
> of processes/threads all actively running.  I suspect something in rmap
> has made its way into 2.6 and our usage pattern is triggering the same
> fault in both places.
> 
> It appears as though the system is unable to efficiently clean up disk
> buffer memory when called on to do so.  In the Documentation/, there
> is mention of a buffermem sysctl, but that's nowhere to be found.
> It's obviously been removed/replaced...  Is there any way to limit the
> amount of buffer memory used by the system, that way if/when kswapd
> needs to reclaim it, there's very little work for it to do?
> 
> Admittedly, that's just masking the problem, as opposed to solving it.
> Any idea why kswapd is having such a tough go??  Known solutions
> for this problem?
> 
> TIA,
> 
> Ken
> 
> -
> 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/
> 


  reply	other threads:[~2003-08-12 19:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12 18:36 High CPU load with kswapd and heavy disk I/O Ken Savage
2003-08-12 19:44 ` Nuno Silva [this message]
2003-08-12 20:23   ` Ken Savage
2003-08-12 23:49     ` Nuno Silva
2003-08-13  0:14       ` Ken Savage
2003-08-13 15:36         ` Nuno Silva
  -- strict thread matches above, loose matches on Subject: below --
2003-08-13 15:34 HABBINGA,ERIK (HP-Loveland,ex1)

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=3F3943B9.7080700@vgertech.com \
    --to=nuno.silva@vgertech.com \
    --cc=kens1835@shaw.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox