mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>,
	Rik van Riel <riel@conectiva.com.br>
Subject: Re: Inclusion of zoned inactive/free shortage patch
Date: Wed, 18 Jul 2001 15:59:30 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0107181555181.1237-100000@penguin.transmeta.com> (raw)
In-Reply-To: <0107190057100H.12129@starship>


On Thu, 19 Jul 2001, Daniel Phillips wrote:
>
> I don't really see much use for inactive_shortage_total() by itself,
> except maybe deciding when to scan vs sitting idle.

Absolutely. But that's an important decision in itself. Getting that
decision wrong means that we either scan too little (and which point the
question of per-zone shortages becomes moot, because by the time we start
scanning we're too deep in trouble to be able to do a good gradual job
anyway). Or we scan too much, and then the per-zone shortage just means
that we'll always have so much inactive stuff in all the zones that we'll
continue scanning forever - because none of the zones (correctly) feel
that they have any reason to actually free anything.

So the global inactive_shortage() decision is certainly an important one:
it should trigger early enough to matter, but not so early that we trigger
it even when most local zones are really totally saturated and we really
shouldn't be scanning at all.

		Linus


  reply	other threads:[~2001-07-18 23:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18  0:30 Marcelo Tosatti
2001-07-18  2:05 ` Linus Torvalds
2001-07-18  1:19   ` Marcelo Tosatti
2001-07-18  3:56     ` Linus Torvalds
2001-07-18  2:56       ` Marcelo Tosatti
2001-07-18  4:55         ` Linus Torvalds
2001-07-18  3:46           ` Marcelo Tosatti
2001-07-18 16:30             ` Linus Torvalds
2001-07-18 20:45               ` Marcelo Tosatti
2001-07-18 22:23                 ` Linus Torvalds
2001-07-18 20:58                   ` Marcelo Tosatti
2001-07-18 22:50                     ` Linus Torvalds
2001-07-18 22:11                       ` Marcelo Tosatti
2001-07-18 22:14                         ` Marcelo Tosatti
2001-07-19  1:02                           ` Linus Torvalds
2001-07-19  7:30                             ` Marcelo Tosatti
2001-07-19 17:12                               ` Linus Torvalds
2001-07-21  2:55                                 ` Marcelo Tosatti
2001-07-18 22:57               ` Daniel Phillips
2001-07-18 22:59                 ` Linus Torvalds [this message]
2001-07-18 23:42                   ` Daniel Phillips
2001-07-19 16:33                     ` Daniel Phillips
2001-07-18 13:27       ` Rik van Riel
2001-07-18 13:23 ` Rik van Riel
2001-07-18 18:22   ` Mike Galbraith
2001-07-18 18:39     ` Rik van Riel
2001-07-18 19:25       ` Mike Galbraith
2001-07-18 20:02         ` Rik van Riel
2001-07-18 21:25           ` Marcelo Tosatti
2001-07-18 19:50   ` Marcelo Tosatti
2001-07-18 21:37     ` Rik van Riel

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.33.0107181555181.1237-100000@penguin.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=phillips@bonn-fries.net \
    --cc=riel@conectiva.com.br \
    /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

all inboxes | Powered by JetHome®