From: Rik van Riel <riel@conectiva.com.br>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Jamie Lokier <lk@tantalophile.demon.co.uk>,
Zlatko Calusic <zlatko@iskon.hr>,
alan@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.rutgers.edu
Subject: Re: shrink_mmap() change in ac-21
Date: Tue, 20 Jun 2000 13:18:38 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0006201258190.12944-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.21.0006200043550.988-100000@inspiron.random>
On Tue, 20 Jun 2000, Andrea Arcangeli wrote:
> On Mon, 19 Jun 2000, Jamie Lokier wrote:
>
> >if those wrong zones are quite full. If the DMA zone desparately needs
> >free pages and keeps needing them, isn't it good to encourage future
> >non-DMA allocations to use another zone? Removing pages from other
>
> After some time the DMA zone will be full again anyway and you
> payed a cost that consists in throwing away unrelated innocent
> pages. I'm not convinced it's the right thing to do.
I didn't know for sure either until I tested -ac21 on my
192MB workstation. The bursts kswapd went through when
it was freeing DMA memory (and 8MB of other memory) have
convinced me that this is not a good idea.
Also, since kswapd stops when all zones have free_pages
above pages_low and we'll free up to pages_high pages of
one zone, it means that we'll:
- allocate the next series of pages from that one zone
with tons of unused pages
- wake up kswapd so we'll free the *next* unused pages
from that zone when we run out of the current batch
- rinse and repeat
This means we'll do a *lot* more allocations from the
less loaded zones than from the other zone, with a few
(short) interruptions by kswapd. Also, there's no need
to throw away data early.
Of course, once we have a scavenge list (in the active
inactive scavenge list VM) this whole point will be moot
and we just want to avoid doing too much IO at once).
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-06-20 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 20:14 Zlatko Calusic
2000-06-19 21:07 ` Rik van Riel
2000-06-19 21:46 ` Jamie Lokier
2000-06-19 22:10 ` Rik van Riel
2000-06-19 22:43 ` Andrea Arcangeli
2000-06-19 22:48 ` Andrea Arcangeli
2000-06-20 9:03 ` Zlatko Calusic
2000-06-20 16:18 ` Rik van Riel [this message]
2000-06-20 16:53 ` Juan J. Quintela
2000-06-20 17:30 ` Manfred Spraul, Juan J. Quintela
2000-06-20 17:41 ` Juan J. Quintela
2000-06-20 19:00 ` Andrea Arcangeli
2000-06-19 21:47 ` Manfred Spraul, Zlatko Calusic
2000-06-20 8:21 ` Zlatko Calusic
2000-06-20 16:14 ` Manfred Spraul, Zlatko Calusic
2000-06-20 17:01 ` willy
2000-06-20 17:03 ` Alan Cox
[not found] <200006202027.NAA01142@penguin.transmeta.com>
2000-06-20 22:59 ` 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.21.0006201258190.12944-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=alan@redhat.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=lk@tantalophile.demon.co.uk \
--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