linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck@vds.kolivas.org, nickpiggin@yahoo.com.au,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Respin: [PATCH] mm: limit lowmem_reserve
Date: Wed, 5 Apr 2006 20:40:09 -0700	[thread overview]
Message-ID: <20060405204009.3235b021.akpm@osdl.org> (raw)
In-Reply-To: <200604061258.40487.kernel@kolivas.org>

Con Kolivas <kernel@kolivas.org> wrote:
>
> On Thursday 06 April 2006 12:55, Con Kolivas wrote:
> > On Thursday 06 April 2006 12:43, Andrew Morton wrote:
> > > Con Kolivas <kernel@kolivas.org> wrote:
> > > > It is possible with a low enough lowmem_reserve ratio to make
> > > >  zone_watermark_ok fail repeatedly if the lower_zone is small enough.
> > >
> > > Is that actually a problem?
> >
> > Every single call to get_page_from_freelist will call on zone reclaim. It
> > seems a problem to me if every call to __alloc_pages will do that?
> 
> every call to __alloc_pages of that zone I mean
> 

One would need to check with the NUMA guys.  zone_reclaim() has a
(lame-looking) timer in there to prevent it from doing too much work.

That, or I'm missing something.  This problem wasn't particularly well
described, sorry.

  reply	other threads:[~2006-04-06  3:41 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-02  4:01 2.6.16-ck3 Con Kolivas
2006-04-02  4:46 ` 2.6.16-ck3 Nick Piggin
2006-04-02  8:51   ` 2.6.16-ck3 Con Kolivas
2006-04-02  9:37     ` 2.6.16-ck3 Nick Piggin
2006-04-02  9:39     ` [ck] 2.6.16-ck3 Con Kolivas
2006-04-02  9:51       ` Nick Piggin
2006-04-03  2:48         ` lowmem_reserve question Con Kolivas
2006-04-03  4:42           ` Mike Galbraith
2006-04-03  4:48             ` Con Kolivas
2006-04-03  4:50               ` [ck] " Con Kolivas
2006-04-03  5:14               ` Mike Galbraith
2006-04-03  5:18                 ` Con Kolivas
2006-04-03  5:31                   ` Mike Galbraith
2006-04-04  2:35           ` [ck] " Con Kolivas
2006-04-06  1:10             ` [PATCH] mm: limit lowmem_reserve Con Kolivas
2006-04-06  1:29               ` Respin: " Con Kolivas
2006-04-06  2:43                 ` Andrew Morton
2006-04-06  2:55                   ` Con Kolivas
2006-04-06  2:58                     ` Con Kolivas
2006-04-06  3:40                       ` Andrew Morton [this message]
2006-04-06  4:36                         ` Con Kolivas
2006-04-06  4:52                           ` Con Kolivas
2006-04-07  6:25               ` Nick Piggin
2006-04-07  9:02                 ` Con Kolivas
2006-04-07 12:40                   ` Nick Piggin
2006-04-08  0:15                     ` Con Kolivas
2006-04-08  0:55                       ` Nick Piggin
2006-04-08  1:01                         ` Con Kolivas
2006-04-08  1:25                           ` Nick Piggin
2006-05-17 14:11                             ` Con Kolivas
2006-05-18  7:11                               ` Nick Piggin
2006-05-18  7:21                                 ` Con Kolivas
2006-05-18  7:26                                   ` Nick Piggin

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=20060405204009.3235b021.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    /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).