public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Mike Black <mblack@csihq.com>,
	tridge@valinux.com, marcelo@conectiva.com.br,
	linux-kernel@vger.kernel.org, riel@conectiva.com.br,
	Andrew Morton <andrewm@uow.edu.au>
Subject: Re: 2.4.8preX VM problems
Date: Sat, 11 Aug 2001 12:06:04 +0000	[thread overview]
Message-ID: <20010811120604.C35@toy.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.21.0108010504160.9379-100000@freak.distro.conectiva> <20010801105419.8F078424A@lists.samba.org> <020001c11a803297110@csihq.com> <01080120392200.00933@starship>
In-Reply-To: <01080120392200.00933@starship>; from phillips@bonn-fries.net on Wed, Aug 01, 2001 at 08:39:22PM +0200

Hi!

> > I have come to the opinion that kswapd needs to be a little smarter
> > -- if it doesn't find anything to swap shouldn't it go to sleep a
> > little longer before trying again?  That way it could gracefully
> > degrade itself when it's not making any progress.
> >
> > In my testing (on a dual 1Ghz/2G machine) the machine "locks up" for
> > long periods of time while kswapd runs around trying to do it's
> > thing. If I could disable kswapd I would just to test this.
> 
> Your wish is my command.  This patch provides a crude-but-effective 
> method of disabling kswapd, using:
> 
>   echo 1 >/proc/sys/kernel/disable_kswapd
> 
> I tested this with dbench and found it runs about half as fast, but 
> runs.  This is reassuring because kswapd is supposed to be doing 
> something useful.

Why not just killall -STOP kswapd?

What is expected state of system without kswapd, BTW? Without kflushd, 
I give up guaranteed time to get data safely to disk [and its usefull
for spindown]. What happens without kswapd?
								Pavel
-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  reply	other threads:[~2001-08-14 11:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01  3:05 2.4.8preX VM problems Andrew Tridgell
2001-08-01  2:26 ` Marcelo Tosatti
2001-08-01  4:37   ` Andrew Tridgell
2001-08-01  3:32     ` Marcelo Tosatti
2001-08-01  5:43       ` Andrew Tridgell
2001-08-01  6:09   ` Andrew Tridgell
2001-08-01  6:10     ` Marcelo Tosatti
2001-08-01  8:13       ` Andrew Tridgell
2001-08-01  8:13         ` Marcelo Tosatti
2001-08-01 10:54           ` Andrew Tridgell
2001-08-01 11:51             ` Mike Black
2001-08-01 18:39               ` Daniel Phillips
2001-08-11 12:06                 ` Pavel Machek [this message]
2001-08-16 21:57                   ` Daniel Phillips
2001-08-04  6:50           ` Anton Blanchard
2001-08-04  5:55             ` Marcelo Tosatti
2001-08-04 17:17               ` Anton Blanchard
2001-08-06 22:58                 ` Marcelo Tosatti
2001-08-07 17:18                   ` Anton Blanchard
2001-08-07 21:02                     ` Kernel 2.4.6 & 2.4.7 networking performance: seeing serious delays in TCP layer depending upon packet length Ron Flory

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=20010811120604.C35@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mblack@csihq.com \
    --cc=phillips@bonn-fries.net \
    --cc=riel@conectiva.com.br \
    --cc=tridge@valinux.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