From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Christopher Zimmerman <zim@av.com>, linux-mm@kvack.org
Subject: Re: More VM balancing issues..
Date: Fri, 17 Mar 2000 15:51:50 -0800 (PST) [thread overview]
Message-ID: <200003172351.PAA37000@google.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10003171523270.987-100000@penguin.transmeta.com> from "Linus Torvalds" at Mar 17, 2000 03:31:52 PM
>
>
> Oh, I found another problem: when the VM balancing was rewritten, the
> "pages_low" thing was still calculated, but nothing actually USED it.
2.3.50 did.
This is one of the things I pointed out in the recent balancing patch.
The patch I sent to Christopher tries to fix it and go back to 2.3.50
bahavior.
Again, Documentation/vm/balance has comments about this which were
true till 2.3.50.
AFAIR, Andrea put this stuff into 2.3, round about 2.3.40 or so timeframe.
>
> So we had three water-marks: "enough for anything", "low on memory" and
> "critical".
>
> And we somehow lost the "low on memory" and only used the "enough" and
> "critical" to do all comparisons.
This was also done properly in 2.3.50, and changed in the recent patch.
Maybe its time that tweaks to the balancing code get documented in
Documentation/vm/balance. Its easier all around to keep track of
what's happening.
Kanoj
>
> Which makes for a _very_ choppy balance, and is definitely wrong.
>
> The behaviour should be something like:
> - whenever we dip below "low", we wake up kswapd. kswapd remains awake
> (for that zone) until we reach "enough".
> - whenever we dip below "critical", we start doing synchronous memory
> freeing ourselves. We continue to do that until we reach "low" again
> (at which point kswapd will still continue in the background, but we
> don't depend on the synchronous freeing any more).
>
> but for some time we appear to have gotten this wrong, and lost the "low"
> mark, and used the "critical" and "high" marks only.
>
> Or maybe somebody did some testing and decided to disagree with the old
> three-level thing based on actual numbers? The only coding I've done has
> been based on "this is how I think it should work, and because I'm always
> right it's obviously the way it _should_ work". Which is not always the
> approach that gets the best results ;)
>
> Linus
>
> --
> 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/
>
--
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/
next prev parent reply other threads:[~2000-03-17 23:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38D2BB5C.AC4A89C9@av.com>
2000-03-17 23:15 ` Linus Torvalds
2000-03-17 23:31 ` Linus Torvalds
2000-03-17 23:51 ` Kanoj Sarcar [this message]
[not found] <38D2A2E3.A2CEA602@av.com>
2000-03-17 22:07 ` Linus Torvalds
2000-03-17 22:23 ` Kanoj Sarcar
2000-03-18 2:59 ` Linus Torvalds
2000-03-20 20:29 ` Kanoj Sarcar
2000-03-20 21:27 ` Linus Torvalds
2000-03-20 22:17 ` Kanoj Sarcar
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=200003172351.PAA37000@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.com \
--cc=zim@av.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