public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jasper Spaans <jasper@spaans.ds9a.nl>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Pau Aliagas <linux4u@wanadoo.es>,
	lkml <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Roberto Orenstein <roberto@brsat.com.br>,
	Francois Romieu <romieu@cogenit.fr>
Subject: Re: [PATCH]  Re: 2.4.9-ac15 painfully sluggish
Date: Tue, 25 Sep 2001 22:42:04 +0200	[thread overview]
Message-ID: <20010925224204.A5968@spaans.ds9a.nl> (raw)
In-Reply-To: <Pine.LNX.4.33.0109251819520.1401-100000@pau.intranet.ct> <Pine.LNX.4.33L.0109251628460.26091-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0109251628460.26091-100000@duckman.distro.conectiva>

On Tue, Sep 25, 2001 at 04:32:13PM -0300, Rik van Riel wrote:

> > The problem seems to be related in pages not moved to swap but
> > being discarded somehow and reread later on.... just a guess.
> 
> I've made a small patch to 2.4.9-ac15 which should make
> page_launder() smoother, make some (very minor) tweaks
> to page aging and updates various comments in vmscan.c
> 
> It's below this email and at:
[snip]

With this -painfully applied- patch, all seems a lot better. However, it
still seems more sluggish than 2.4.9-ac12.

Haven't bothered testing -ac13 and -ac14.

Swapping still seems to be a problem though, as this kernel happily claims
several tens of MBs of swap, and then, out of the blue, starts writing pages
out in huge blocks.

The vmstat info just disappeared from my screen, while stressing the
vm-system by doing a large parallel build, however, it showed no paging
happening during long times (20-30 secs) and then suddenly writing 30 MB in
one go.

Doesn't seem very smooth to me, where can I get my refund? :)

(if you'd like more details, please ask, I can do some testing)

Regards,
-- 
  Q_.           Jasper Spaans <jasper@spaans.ds9a.nl>
 `~\            http://jsp.ds9a.nl/
Mr /\           Tel/Fax: +31-84-8749842
Zap             Move '.sig' for great justice!

  reply	other threads:[~2001-09-25 20:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25 15:36 2.4.9-ac15 painfully sluggish Pau Aliagas
2001-09-25 16:16 ` Rik van Riel
2001-09-25 16:25   ` Pau Aliagas
2001-09-25 16:37     ` Rik van Riel
2001-09-25 17:04       ` Pau Aliagas
2001-09-25 17:31         ` Rik van Riel
2001-09-25 18:01           ` Pau Aliagas
2001-09-25 19:32     ` [PATCH] " Rik van Riel
2001-09-25 20:42       ` Jasper Spaans [this message]
2001-09-25 20:52         ` Rik van Riel
2001-09-26  7:36       ` Pau Aliagas
2001-09-26 13:54       ` [PATCH] " Roberto Orenstein
2001-09-26 18:01       ` [PATCH] " Kent Borg
  -- strict thread matches above, loose matches on Subject: below --
2001-09-27  4:27 Thomas Hood
2001-09-27 12:01 ` Alan Cox

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=20010925224204.A5968@spaans.ds9a.nl \
    --to=jasper@spaans.ds9a.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux4u@wanadoo.es \
    --cc=riel@conectiva.com.br \
    --cc=roberto@brsat.com.br \
    --cc=romieu@cogenit.fr \
    /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