linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Zlatko Calusic <zlatko@iskon.hr>, linux-mm@kvack.org
Subject: Re: pre2 swap_out() changes
Date: Fri, 12 Jan 2001 16:45:17 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.10.10101121641520.8097-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101122038420.10842-100000@freak.distro.conectiva>


On Fri, 12 Jan 2001, Marcelo Tosatti wrote:
> 
> On Fri, 12 Jan 2001, Linus Torvalds wrote:
> 
> > If the page truly is new (because of some other user), then page_launder()
> > won't drop it, and it doesn't matter. But dropping it from the VM means
> > that the list handling can work right, and that the page will be aged (and
> > thrown out) at the same rate as other pages.
> 
> What about the amount of faults this potentially causes? 

It only increases the number of faults on low-memory machines where the VM
has been found to be one cause of mm pressure (otherwise we never get
here: if page_launder() is able to relieve the memory pressure we'll never
even try to swap anything out).

Basically, it increases the number of soft pagefaults (the ones where we
can find the thing in the page cache) only, and only under the one
circumstance when that soft page-fault itself is going to give us more
information about page usage (ie it will help pinpoint the processes with
big memory footprints - and can make us able to slow those down in favour
of the well-behaved applications).

So I consider it to be potentially a win, not a loss. We'll see.

		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/

  reply	other threads:[~2001-01-13  0:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 10:38 Marcelo Tosatti
2001-01-11 18:49 ` Linus Torvalds
2001-01-12 11:35   ` Zlatko Calusic
2001-01-12 19:45     ` Linus Torvalds
2001-01-12 19:22       ` Marcelo Tosatti
2001-01-13  0:23         ` Linus Torvalds
2001-01-12 22:41           ` Marcelo Tosatti
2001-01-13  0:45             ` Linus Torvalds [this message]
2001-01-17  7:05             ` Rik van Riel
2001-01-18 11:54           ` Rik van Riel
2001-01-13 11:41         ` Zlatko Calusic
2001-01-17  7:08           ` Rik van Riel
2001-01-13 11:51       ` Zlatko Calusic
2001-01-14  2:39         ` Marcelo Tosatti
2001-01-14  4:36           ` Linus Torvalds
2001-01-14  3:50             ` Marcelo Tosatti
2001-01-14 15:51               ` Ed Tomlinson
2001-01-14 14:13                 ` Marcelo Tosatti
2001-01-14 16:15                   ` Zlatko Calusic
2001-01-14 17:22                     ` Zlatko Calusic
2001-01-17  7:16                       ` Rik van Riel
2001-01-17  7:15                 ` Rik van Riel
2001-01-17  7:12               ` Rik van Riel
2001-01-11 20:52 Benjamin Redelings I

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.10101121641520.8097-100000@penguin.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    --cc=zlatko@iskon.hr \
    /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