From: Rik van Riel <riel@conectiva.com.br>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Rajagopal Ananthanarayanan <ananth@sgi.com>,
Benjamin Redelings I <bredelin@ucla.edu>,
linux-mm@kvack.org
Subject: Re: [DATAPOINT] pre7-6 will not swap
Date: Sun, 7 May 2000 14:40:37 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0005071418520.8605-100000@duckman.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.10.10005061905180.29159-100000@cesium.transmeta.com>
On Sat, 6 May 2000, Linus Torvalds wrote:
> My personal inclination is along the lines of
> - we never really care about any particular zone. We should make sure
> that all zones get balanced, and that is what running kswapd will
> eventually cause.
> - things like "shrink_mmap" and "vmscan" should both free any page from
> any zone that is (a) a good candidateand (b) the zone is not yet
> well-balanced.
double-nod
> - looking at "shrink_mmap()", my reaction would not be to add more
> complexity to it, but to remove the _one_ special case that looks at
> one specific zone:
>
> /* wrong zone? not looped too often? roll again... */
> if (page->zone != zone && count)
> goto again;
>
> I would suggest just removing that test altogether. The page wasn't
> from a "wrong zone". It was just a different zone that also needed
> balancing.
The danger in this is that we could "use up" the remaining
ticks on the count variable in do_try_to_free_pages() and
end up with a failed rmqueue for the request...
Oh, and the return value for shrink_mmap() will still
indicate success, even if we failed to free a page for
the zone we intended ... we've already decided for that
before we get into the loop or not.
But I agree that this test is wrong; it makes shrink_mmap()
loop to often compared to swap_out(), leading to worse page
aging in the swap cache and increased cpu use.
The solution could be to let do_try_to_free_page() loop
more often than it does now ... increasing our chances
of freeing from the right zone while at the same time
not increasing the amount of work to be done (we need
to do it anyway, so why not do it now and have that
memory allocation succeed?)
regards,
Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.
Wanna talk about the kernel? irc.openprojects.net / #kernelnewbies
http://www.conectiva.com/ http://www.surriel.com/
--
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-05-07 17:40 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 [this message]
2000-05-07 17:53 ` Linus Torvalds
2000-05-07 19:13 ` Rajagopal Ananthanarayanan
2000-05-07 19:30 ` Linus Torvalds
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.21.0005071418520.8605-100000@duckman.conectiva \
--to=riel@conectiva.com.br \
--cc=ananth@sgi.com \
--cc=bredelin@ucla.edu \
--cc=linux-mm@kvack.org \
--cc=riel@nl.linux.org \
--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