linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Roger Larsson <roger.larsson@norran.net>
To: Cesar Eduardo Barros <cesarb@nitnet.com.br>
Cc: linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: Re: kswapd eating too much CPU on ac16/ac18
Date: Sat, 17 Jun 2000 23:34:55 +0200	[thread overview]
Message-ID: <394BEEFF.C194F59E@norran.net> (raw)
In-Reply-To: <20000617164317.A9421@cesarb.personal>

Hi,

The reason for me to ask you to remove it is since there are two
problems
related to this code snippet. (Reported earlier on linux-mm)

* If no zone has pressure - we will loop "forever" since no pages will
pass
this test. (On a 16 MB machine this is the likely scenario)

* If there are no pages of a zone with pressure are on LRU - we will
loop...

And since there is no guarantee that shrink_mmap is not called in these
circumstances...

I have released patches (on linux-mm) that tries to handle these
situations.
* do_try_to_free_pages avoids to call shrink_mmap with no pressure.
* shrink_mmap tries to determine the bad situation (not in my latest)

/RogerL


Cesar Eduardo Barros wrote:
> 
> > Please try to remove only this test to get a comparable result.
> 
> I nuked the whole block:
> 
>                 /*
>                  * Page is from a zone we don't care about.
>                  * Don't drop page cache entries in vain.
>                  */
>                 if (page->zone->free_pages > page->zone->pages_high) {
>                         /* the page from the wrong zone doesn't count */
>                         count++;
>                         goto unlock_continue;
>                 }
> 
> Commenting it out made ac19 perform almost as good as ac4 (it looked a bit
> faster).
> 
> I don't know how it would affect boxes with more than one zone, but my gut
> feeling is that it won't hurt and might make them even a bit faster.
> 
> --
> Cesar Eduardo Barros
> cesarb@nitnet.com.br
> cesarb@dcc.ufrj.br
> --
> 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/

--
Home page:
  http://www.norran.net/nra02596/
--
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/

  reply	other threads:[~2000-06-17 21:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-17 19:43 Cesar Eduardo Barros
2000-06-17 21:34 ` Roger Larsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-16  9:56 Roger Larsson
2000-06-13 23:51 Cesar Eduardo Barros
2000-06-14  0:00 ` Alan Cox
2000-06-14  0:10   ` Cesar Eduardo Barros
2000-06-16  5:45   ` Mike Galbraith
2000-06-16 15:08     ` Rik van Riel
2000-06-17  3:05       ` Cesar Eduardo Barros
2000-06-17  4:04         ` Mike Galbraith
2000-06-17 14:06           ` Cesar Eduardo Barros
2000-06-17 15:25             ` Mike Galbraith
2000-06-17 15:23           ` Rik van Riel
2000-06-17 15:33         ` Rik van Riel
2000-06-19 21:22           ` Goswin Brederlow
2000-06-18  6:26       ` Mike Galbraith

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=394BEEFF.C194F59E@norran.net \
    --to=roger.larsson@norran.net \
    --cc=cesarb@nitnet.com.br \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.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