linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rohit Seth <rohit.seth@intel.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: akpm@osdl.org, linux-mm@kvack.org,
	Mattia Dongili <malattia@linux.it>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] Reset the high water marks in CPUs pcp list
Date: Wed, 28 Sep 2005 13:26:25 -0700	[thread overview]
Message-ID: <1127939185.5046.17.camel@akash.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0509281259550.14892@schroedinger.engr.sgi.com>

On Wed, 2005-09-28 at 13:01 -0700, Christoph Lameter wrote:
> On Wed, 28 Sep 2005, Seth, Rohit wrote:
> 
> > Recent changes in page allocations for pcps has increased the high watermark for these lists.  This has resulted in scenarios where pcp lists could be having bigger number of free pages even under low memory conditions. 
> > 
> >  	[PATCH]: Reduce the high mark in cpu's pcp lists.
> 
> There is no need for such a patch. The pcp lists are regularly flushed.
> See drain_remote_pages.

CONFIG_NUMA needs to be defined for that.  And then too for flushing the
remote pages.  Also, when are you flushing the local pcps.  Also note
that this patch is just bringing the free pages on the pcp list closer
to what used to be the number earlier.

-rohit


  reply	other threads:[~2005-09-28 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 17:50 [patch] Reset the high water marks in CPUs pcp list Seth, Rohit
2005-09-28 20:01 ` Christoph Lameter
2005-09-28 20:26   ` Rohit Seth [this message]
2005-09-28 21:09     ` Christoph Lameter
2005-09-28 21:32       ` Rohit Seth
2005-09-28 21:56         ` Christoph Lameter
2005-09-29  1:12           ` Rohit Seth
2005-09-29  6:49           ` Nick Piggin
2005-09-29 16:34             ` Rohit Seth
2005-09-28 21:18   ` Martin J. Bligh
2005-09-28 21:55     ` Christoph Lameter

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=1127939185.5046.17.camel@akash.sc.intel.com \
    --to=rohit.seth@intel.com \
    --cc=akpm@osdl.org \
    --cc=clameter@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=malattia@linux.it \
    /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).