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 02:27:26 +0100 [thread overview]
Message-ID: <20010124022726.D1201@athlon.random> (raw)
In-Reply-To: <20010124010936.A1201@athlon.random> <Pine.LNX.4.30.0101240126500.3522-100000@iq.rulez.org>
In-Reply-To: <Pine.LNX.4.30.0101240126500.3522-100000@iq.rulez.org>; from sape@iq.rulez.org on Wed, Jan 24, 2001 at 01:43:26AM +0100
On Wed, Jan 24, 2001 at 01:43:26AM +0100, Sasi Peter wrote:
> (30+ high speed streams from 4 disks does really need some caching).
This isn't obvious. Your working may not fit in cache and so the kernel
understand it's worthless to swapout stuff to make space to a polluted cache.
> Can't say, of these many daemons nothing can be swapped out (and should
> under I/O load)!
If you run `cp /dev/zero .` on a smart VM nothing must be swapped out even if
it generated nearly the maximal I/O flood possible. It's worthless to let a
polluted cache to grow. It won't help anyways and you'll run slower the next
time you'll have to pagein from swap.
It _enterely_ depends on the I/O load pattern if it worth to swapout or not
to make space for filesystem cache.
> The performance just used to be better, but the whole more instable.
>
> Be this, if this is the price for stability.
As said we can add bits of page aging (that can't destabilize anything and it
will only affect performance behaviour), but I'd prefer to be sure you really
get a slowdown due the new VM behaviour (because more aging if done without
multiqueue O(1) approch can introduces waste of CPU and cachelines in kernel
space), so could you try to kill notes and squid and the other unused stuff and
to see if you return to deliver performance as with the older kernels? I still
miss this important information (last thing you said me was that with 100mbyte
in cache it swapouts, and without knowing the details of the I/O pattern it
looked sane). After that I'd also like to know what happens with 2.4.0 that
uses multiqueue and that is also able to detect pollution and to avoid swapping
out in such case.
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/
next prev parent reply other threads:[~2001-01-24 1:27 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
2001-01-24 0:43 ` Sasi Peter
2001-01-24 1:27 ` Andrea Arcangeli [this message]
-- 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=20010124022726.D1201@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