From: Andrea Arcangeli <andrea@suse.de>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: [PATCH] 2.2.14 VM fix #3
Date: Tue, 25 Jan 2000 10:08:58 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.10.10001250959170.12802-100000@d251.suse.de> (raw)
In-Reply-To: <14476.42622.777454.521474@dukat.scot.redhat.com>
On Mon, 24 Jan 2000, Stephen C. Tweedie wrote:
>> And the 1-second polling loop has to be killed since it make no sense.
>
>Actually, that probably isn't too bad, as long as we make sure we wake
Agreed. It definitely isn't too bad. But as far I can tell it shouldn't
help either in RL and performance would be better without it. The point of
the 1 second polling loop basically is to refill the freelist from the low
to the high watermark even if the last allocation didn't caused the
watermark to go below the "low" level.
I think it would be better to make sure that kswapd will do a high-low
work at each run and not a not interesting 2/3 page work (for obvious
icache-lines reasons). And kswapd is so fast freeing the high-low pages,
that 1 second is a too long measure to make a RL difference. We just made
sure to not block on allocations before we go below the "min" level, thus
kswapd will have all the time to do its work before we block (if the mem
load is not heavy, and if the load is heavy the 1 second polling loop was
just a noop in the first place ;).
Andrea
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
prev parent reply other threads:[~2000-01-25 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-21 4:07 Rik van Riel
2000-01-21 13:34 ` Andrea Arcangeli
2000-01-24 19:22 ` Stephen C. Tweedie
2000-01-24 22:38 ` Rik van Riel
2000-01-25 9:08 ` Andrea Arcangeli [this message]
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=Pine.LNX.4.10.10001250959170.12802-100000@d251.suse.de \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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