From: Kanoj Sarcar <kanojsarcar@yahoo.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Cc: Rik van Riel <riel@conectiva.com.br>,
Dirk Wetter <dirkw@rentec.com>,
Mike Galbraith <mikeg@wen-online.de>,
linux-mm@kvack.org, "Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: [PATCH] Separate global/perzone inactive/free shortage
Date: Mon, 16 Jul 2001 08:51:26 -0700 (PDT) [thread overview]
Message-ID: <20010716155126.37887.qmail@web14306.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0107140204110.4153-100000@freak.distro.conectiva>
--- Marcelo Tosatti <marcelo@conectiva.com.br> wrote:
> Hi,
>
> As well known, the VM does not make a distiction
> between global and
> per-zone shortages when trying to free memory. That
> means if only a given
> memory zone is under shortage, the kernel will scan
> pages from all zones.
>
> The following patch (against 2.4.6-ac2), changes the
> kernel behaviour to
> avoid freeing pages from zones which do not have an
> inactive and/or
> free shortage.
>
> Now I'm able to run memory hogs allocating 4GB of
> memory (on 4GB machine)
> without getting real long hangs on my ssh session.
> (which used to happen
> on stock -ac2 due to exhaustion of DMA pages for
> networking).
>
> Comments ?
>
> Dirk, Can you please try the patch and tell us if it
> fixes your problem ?
>
>
Just a quick note. A per-zone page reclamation
method like this was what I had advocated and sent
patches to Linus for in the 2.3.43 time frame or so.
I think later performance work ripped out that work.
I guess the problem is that a lot of the different
page reclamation schemes first of all do not know
how to reclaim pages for a specific zone, and secondly
have to go thru a lot of work before they discover the
page they are trying to reclaim does not belong to the
shortage zone, hence wasting a lot of work/cputime.
try_to_swap_out is a good example, which can be solved
by rmaps.
Kanoj
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.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-mm.org/
next prev parent reply other threads:[~2001-07-16 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-14 5:19 Marcelo Tosatti
2001-07-14 7:11 ` Marcelo Tosatti
2001-07-14 20:13 ` Dirk
[not found] ` <Pine.LNX.4.33.0107141023440.283-100000@mikeg.weiden.de>
2001-07-16 13:19 ` Stephen C. Tweedie
2001-07-16 15:44 ` Mike Galbraith
2001-07-16 18:30 ` Stephen C. Tweedie
2001-07-17 2:55 ` Mike Galbraith
2001-07-16 18:42 ` Dirk Wetter
2001-07-16 15:51 ` Kanoj Sarcar [this message]
2001-07-16 19:00 ` Rik van Riel
2001-07-17 0:27 ` Marcelo Tosatti
2001-07-17 2:07 ` Kanoj Sarcar
2001-07-17 0:01 ` Marcelo Tosatti
2001-07-16 13:56 Bulent Abali
2001-07-16 15:56 ` Stephen C. Tweedie
2001-07-16 19:04 ` Rik van Riel
2001-07-18 8:54 ` Mike Galbraith
2001-07-18 10:18 ` Stephen C. Tweedie
2001-07-18 14:51 ` Mike Galbraith
2001-07-18 15:07 ` Dave McCracken
2001-07-18 16:09 ` 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=20010716155126.37887.qmail@web14306.mail.yahoo.com \
--to=kanojsarcar@yahoo.com \
--cc=dirkw@rentec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=mikeg@wen-online.de \
--cc=riel@conectiva.com.br \
--cc=sct@redhat.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