public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org,
	Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: ZVC: Increase threshold for larger processor configurationss
Date: Thu, 29 Jun 2006 23:31:51 -0700	[thread overview]
Message-ID: <20060629233151.31a12d81.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606292314580.31091@schroedinger.engr.sgi.com>

On Thu, 29 Jun 2006 23:15:55 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:

> On Thu, 29 Jun 2006, Christoph Lameter wrote:
> 
> > > Did you consider my earlier suggestion about these counters?  That, over the
> > > short-term, they tend to count in only one direction?  So we can do
> > Uhh... We are overcompensating right? Pretty funky idea that is new to me 
> > and that would require some thought.
> > 
> > This would basically increase the stepping by 50% if we are only going in 
> > one direction.
> 
> A patch that does this:
> 
> 
> ZVC: overcompensate while incrementing ZVC counters
> 
> Overcompensate by a balance factor when incrementing or decrementing
> ZVC counters anticipating continual increase in the same direction.

Looks sensible.

Please check that none of this is racy wrt memory hotplug
(process_zones->vm_stat_setup).

> Note that I have not been able to see any effect off this approach on
> an 8p system where I tested this.
> I probably will have a chance to test it on larger systems (160p) tomorrow.

OK.  But let's not rush - it's only fine-tuning.  I'm thinking we should
get what we have in -mm4 into -rc1 - I think it's stable enough, and we
don't want to be carrying all those changes splatered across the VM for the
next two months.  Let's aim to get the well-measured fine-tuning in place
for -rc2, OK?

Are you aware of any to-do items remaining in the -mm4 patches?  The NFS
changes need a review from Trond - hopefully he'll be able to find 5-10
minutes to do that sometime?

  reply	other threads:[~2006-06-30  6:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 17:41 ZVC: Increase threshold for larger processor configurationss Christoph Lameter
2006-06-28 22:49 ` Andrew Morton
2006-06-29 18:22   ` Christoph Lameter
2006-06-29 18:57     ` Andrew Morton
2006-06-30 17:15       ` Christoph Lameter
2006-06-30  6:14     ` Christoph Lameter
2006-06-30  6:15     ` Christoph Lameter
2006-06-30  6:31       ` Andrew Morton [this message]
2006-06-30  7:17         ` 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=20060629233151.31a12d81.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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