From: Rohit Seth <rohit.seth@intel.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
akpm@osdl.org, linux-mm@kvack.org,
Mattia Dongili <malattia@linux.it>,
linux-kernel@vger.kernel.org, steiner@sgi.com
Subject: Re: [patch] Reset the high water marks in CPUs pcp list
Date: Thu, 29 Sep 2005 09:34:19 -0700 [thread overview]
Message-ID: <1128011659.3735.3.camel@akash.sc.intel.com> (raw)
In-Reply-To: <433B8E76.9080005@yahoo.com.au>
On Thu, 2005-09-29 at 16:49 +1000, Nick Piggin wrote:
> I don't see that there would be any problems with playing with the
> ->high and ->low numbers so long as they are a reasonable multiple
> of batch, however I would question the merit of setting the high
> watermark of the cold queue to ->batch + 1 (should really stay at
> 2*batch IMO).
>
I agree that this watermark is little low at this point. But that is
mainly because currently we don't have a way to drain the pcps for low
memory conditions. Once I add that support, I will bump up the high
water marks.
Can you share a list of specific workloads that you ran earlier while
fixing these numbers.
-rohit
next prev parent reply other threads:[~2005-09-29 16:27 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
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 [this message]
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=1128011659.3735.3.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 \
--cc=nickpiggin@yahoo.com.au \
--cc=steiner@sgi.com \
/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).