public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.>=13 VM/kswapd/shmem/Oracle issue (was Re: Google's mm problems)
Date: Sat, 17 Nov 2001 16:54:41 +0100	[thread overview]
Message-ID: <20011117165441.S1381@athlon.random> (raw)
In-Reply-To: <E15yhyY-0000Yb-00@starship.berlin> <20011109033851.A15099@asooo.flowerfire.com> <20011115184036.D1381@athlon.random> <3BF3FFF4.A4768C43@redhat.com>
In-Reply-To: <3BF3FFF4.A4768C43@redhat.com>; from arjanv@redhat.com on Thu, Nov 15, 2001 at 05:48:36PM +0000

[ sorry for the delay ]

On Thu, Nov 15, 2001 at 05:48:36PM +0000, Arjan van de Ven wrote:
> Andrea Arcangeli wrote:
> 
> > loop that can trigger with the -ac VM when all the ZONE_DMA is
> > unfreeable (now fixed in mainline with classzone) have nothing to do
> 
> Ok I think I've misunderstood classzone then.
> As I understand it, it prevents looping in ZONE_NORMAL when ZONE_DMA has
> memory free,
> and looping in ZONE_HIGHMEM if ZONE_NORMAL or ZONE_DMA have memory free.

correct.

> Can you please explain how it also solves the ZONE_DMA problem ? 

It also solves the ZONE_DMA problem with the ->need_balance trigger in
combination with the classzone logic.

With classzone in combination with the need_balance kswapd will never
ever waste time trying to balance a never used classzone. 

If all your hardware is PCI nobody will make an allocation from the
ZONE_DMA classzone and so kswapd will never loop on the ZONE_DMA, as
instead can happen with -ac as soon as the ZONE_DMA becomes unfreeable
and under the low watermark (and "unfreeable" of course also means all
anon not locked memory but no swap installed in the machine).

Andrea

  reply	other threads:[~2001-11-17 15:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30 23:07 Google's mm problems Daniel Phillips
2001-11-01 20:00 ` Google's mm problems with 2.4.13 and 4G of memory Sven Heinicke
2001-11-02 22:24   ` Daniel Phillips
2001-11-03 20:56 ` Google's mm problems Christian Ehrhardt
2001-11-04  3:29   ` Daniel Phillips
2001-11-05 16:10     ` Sven Heinicke
2001-11-09  9:38 ` 2.4.>=13 VM/kswapd/shmem/Oracle issue (was Re: Google's mm problems) Ken Brownfield
2001-11-09 22:39   ` vda
2001-11-15 17:40   ` Andrea Arcangeli
2001-11-15 17:48     ` Arjan van de Ven
2001-11-17 15:54       ` Andrea Arcangeli [this message]
2001-11-18  6:17         ` Mike Galbraith
2001-11-18  6:27           ` Andrea Arcangeli
2001-11-18  7:14             ` Mike Galbraith
2001-11-15 20:07     ` Ken Brownfield

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=20011117165441.S1381@athlon.random \
    --to=andrea@suse.de \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.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