public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Linus Torvalds <torvalds@transmeta.com>
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: Thu, 19 Jul 2001 18:33:26 +0200	[thread overview]
Message-ID: <01071918332601.00317@starship> (raw)
In-Reply-To: <Pine.LNX.4.33.0107181555181.1237-100000@penguin.transmeta.com> <0107190142450I.12129@starship>
In-Reply-To: <0107190142450I.12129@starship>

On Thursday 19 July 2001 01:42, Daniel Phillips wrote:
> Yes.  The inactive shortage needs to be a function of the length of
> the inactive_dirty queue rather than just the amount that free pages
> is less than some fixed minimum.

Oops, it already is, good :-]

> The target length of the
> inactive_dirty queue in turn can be a function of the global free
> shortage (which is where the minimum free numbers get used)

ditto, it's already that way...

> and the transfer rate of the disk(s).

This we don't do, and afaics, this is the only way to get stability
across a really wide range of loads, and on system configurations we 
can't possibly pre-tune for.

> Again, experimental - without careful
> work a feedback mechanism like this could oscillate wildly.  It's
> most probably the way forward in the long run though.
>
> --
> Daniel

  reply	other threads:[~2001-07-19 16:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18  0:30 Inclusion of zoned inactive/free shortage patch 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
2001-07-18 23:42                   ` Daniel Phillips
2001-07-19 16:33                     ` Daniel Phillips [this message]
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=01071918332601.00317@starship \
    --to=phillips@bonn-fries.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=riel@conectiva.com.br \
    --cc=torvalds@transmeta.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