linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <Linux-Kernel@Vger.Kernel.ORG>
Subject: Re: [PATCH] 1/5 VM changes: zone-pressure.patch
Date: Thu, 17 Jul 2003 17:50:44 +0400	[thread overview]
Message-ID: <16150.43444.734717.485697@laputa.namesys.com> (raw)
In-Reply-To: <20030709034251.6902c488.akpm@osdl.org>

Andrew Morton writes:
 > Nikita Danilov <Nikita@Namesys.COM> wrote:
 > >
 > >  > OK, fixes a bug.
 > > 
 > >  What bug?
 > 
 > Failing to consider mapped pages on the active list until the scanning
 > priority gets large.
 > 
 > I ran up your five patches on a 256MB box, running `qsbench -m 350'.  It got
 > all slow then the machine seized up.   I'll poke at it some.
 > 

My understanding of this is following:

1. kswapd/balance_pgdat runs through all priorities, but fails to rise
zone->free_pages above zone->pages_min. So it exet. Which is strange.

2. nobody is going to wake it up, because all memory allocators are
looping indefinitely in that newly introduced do_retry loop inside
__alloc_pages.

I think either wakeup_kswapd() should be called in __alloc_pages()
before goto rebalance, or kswapd should loop until it restores all zones
to the balance (actually, comment before balance_pgdat() says it does),
or both.

Nikita.

  parent reply	other threads:[~2003-07-17 13:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09  8:46 [PATCH] 1/5 VM changes: zone-pressure.patch Nikita Danilov
2003-07-09 10:12 ` Andrew Morton
2003-07-09 10:20   ` Nikita Danilov
2003-07-09 10:42     ` Andrew Morton
2003-07-09 11:19       ` Nikita Danilov
2003-07-10 14:40       ` Martin Schlemmer
2003-07-17 13:50       ` Nikita Danilov [this message]
2003-07-09 10:22 ` Andrew Morton
2003-07-09 10:30   ` Nikita Danilov

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=16150.43444.734717.485697@laputa.namesys.com \
    --to=nikita@namesys.com \
    --cc=Linux-Kernel@Vger.Kernel.ORG \
    --cc=akpm@osdl.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;
as well as URLs for NNTP newsgroup(s).