linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: Rajagopal Ananthanarayanan <ananth@sgi.com>
Cc: riel@nl.linux.org, Benjamin Redelings I <bredelin@ucla.edu>,
	linux-mm@kvack.org
Subject: Re: [DATAPOINT] pre7-6 will not swap
Date: Sun, 7 May 2000 12:30:15 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10005071227160.30202-100000@cesium.transmeta.com> (raw)
In-Reply-To: <3915C053.EE77396C@sgi.com>


On Sun, 7 May 2000, Rajagopal Ananthanarayanan wrote:
> 
> In the presense unreferenced pages in zones with free_pages > pages_high,
> should shrink_mmap ever fail? Current shrink_mmap will
> always skip over the pages of such zones. This in turn
> can lead to swapping.

I think shrink_mmap() should fail for that case: it tells the logic that
calls it that its time to stop calling shrink_mmap(), and go to vmscan
instead (so that next time we call shrink_mmap, we may in fact find some
pages to free).

If there really are tons of pages with free_pages > pages_high, then we
must have called shrink_mmap() for some other reason, so we're probably
interested in another zone altogether that isn't even a subset of the
"tons of memory" case (because if we had been interested in any class that
has the "lots of free memory" zone as a subset, then the logic in
__alloc_pages() would just have allocated it directly without worrying
about zone balancing at all).

		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:[~2000-05-07 19:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8evk0f$7jote$1@fido.engr.sgi.com>
2000-05-06 17:12 ` Rajagopal Ananthanarayanan
2000-05-06  4:25   ` Benjamin Redelings I
2000-05-06 19:35   ` Linus Torvalds
2000-05-06  5:35     ` Benjamin Redelings I
2000-05-06 21:46       ` Rik van Riel
2000-05-06 22:24         ` Rajagopal Ananthanarayanan
2000-05-06 14:03           ` Benjamin Redelings I
2000-05-07  0:22           ` Rik van Riel
2000-05-07  2:23           ` Linus Torvalds
2000-05-07 17:40             ` Rik van Riel
2000-05-07 17:53               ` Linus Torvalds
2000-05-07 19:13                 ` Rajagopal Ananthanarayanan
2000-05-07 19:30                   ` Linus Torvalds [this message]
2000-05-08 20:40                     ` gprof data for pre7-6 Rajagopal Ananthanarayanan
2000-05-09  1:52     ` [DATAPOINT] pre7-6 will not swap Quintela Carreira Juan J.
2000-05-09  2:28       ` Rajagopal Ananthanarayanan
2000-05-09  2:33       ` Linus Torvalds
2000-05-09  3:31         ` Rajagopal Ananthanarayanan
2000-05-09 15:56           ` [DATAPOINT] pre7-8 swaps with FREE mem? Benjamin Redelings I
2000-05-06 20:12   ` PG_referenced and lru_cache (cpu%) Roger Larsson
2000-05-06 18:31     ` Rik van Riel
2000-05-06 22:16       ` Roger Larsson
2000-05-05  8:07 [DATAPOINT] pre7-6 will not swap 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.10005071227160.30202-100000@cesium.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=ananth@sgi.com \
    --cc=bredelin@ucla.edu \
    --cc=linux-mm@kvack.org \
    --cc=riel@nl.linux.org \
    /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