public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Sasi Peter <sape@iq.rulez.org>
Cc: Godfrey Livingstone <godfrey@hattaway-associates.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Ingo's RAID patch for 2.2.18 final?
Date: Wed, 24 Jan 2001 01:09:36 +0100	[thread overview]
Message-ID: <20010124010936.A1201@athlon.random> (raw)
In-Reply-To: <3A61315C.37318059@hattaway-associates.com> <Pine.LNX.4.30.0101240044040.3522-100000@iq.rulez.org>
In-Reply-To: <Pine.LNX.4.30.0101240044040.3522-100000@iq.rulez.org>; from sape@iq.rulez.org on Wed, Jan 24, 2001 at 12:52:57AM +0100

On Wed, Jan 24, 2001 at 12:52:57AM +0100, Sasi Peter wrote:
> On Sun, 14 Jan 2001, Godfrey Livingstone wrote:
> 
> > You MUST apply this patch before the two raid patches. The VM patch stablises
> > the 2.2.18 virtual memory system and if you don't apply my two repackaged
> > patches will fail. The above VM patch has been accepted into 2.2.19pre3 and
> > many people are using it so is not untested.
> 
> 2.2.19preXaaX Virtually disabled I/O cache extention-by-swapout, working
> on previous (semi)stock kernels (raid+ide patched) :(

Can you measure a performance degradation because of that? Previous kernels was
certainly not a good example because they was swapping out stuff even with
`cp /dev/zero .`.

> Thus I wouldn't advise VM global till it gets somewhatbalanced to
> non-swapless configs...

You said me your machine start to swapout when the filesystem cache reaches
100mbytes (on your 384Mbyte box). That seems sane behaviour on a misc load. We
could add some additional bit of page aging to swapout more when it worth
indeed, but current balance looks just quite sane.

Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-24  0:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 21:36 Ingo's RAID patch for 2.2.18 final? Jens Petersohn
2001-01-11 22:22 ` Takacs Sandor
2001-01-11 22:27   ` Alan Cox
2001-01-11 22:42     ` Takacs Sandor
2001-01-11 22:48       ` Jens Petersohn
2001-01-11 23:14         ` Takacs Sandor
2001-01-11 23:56       ` Matthias Kilian
2001-01-12 15:20       ` Oliver Teuber
2001-01-12  1:30 ` Andrea Arcangeli
2001-01-14  4:55 ` Godfrey Livingstone
2001-01-14  7:54   ` junio
2001-01-14 12:35     ` Ingo Molnar
2001-01-23 23:52   ` Sasi Peter
2001-01-24  0:09     ` Andrea Arcangeli [this message]
2001-01-24  0:43       ` Sasi Peter
2001-01-24  1:27         ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2001-01-24 15:05 Sasi Peter
2001-02-16 14:17 ` Andrea Arcangeli
2001-02-16 15:53   ` David Mansfield
2001-02-17 19:23     ` Andrea Arcangeli

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=20010124010936.A1201@athlon.random \
    --to=andrea@suse.de \
    --cc=godfrey@hattaway-associates.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sape@iq.rulez.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