From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Paul Jackson <pj@sgi.com>
Cc: clameter@sgi.com, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Avoid allocating during interleave from almost full nodes
Date: Wed, 08 Nov 2006 18:09:10 +0100 [thread overview]
Message-ID: <1163005750.14238.19.camel@twins> (raw)
In-Reply-To: <20061108090644.f23d37de.pj@sgi.com>
On Wed, 2006-11-08 at 09:06 -0800, Paul Jackson wrote:
> Peter wrote:
> > global fault counter
>
> I hope we avoid frequently updated, widely accessed global
> counters. They tend to create hot cache lines on big NUMA
> boxes.
>
> Christoph said that the counters he was suggesting were
> node or cpu local. That sounds good to me.
Very true indeed, I was just hoping we could come up with 1 vm-time; but
perhaps the local vs global thing will keep us from that.
next prev parent reply other threads:[~2006-11-08 17:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 20:58 Avoid allocating during interleave from almost full nodes Christoph Lameter
2006-11-03 21:46 ` Andrew Morton
2006-11-03 22:10 ` Christoph Lameter
2006-11-03 22:31 ` Andrew Morton
2006-11-04 0:28 ` Christoph Lameter
2006-11-04 0:58 ` Andrew Morton
2006-11-06 16:53 ` Christoph Lameter
2006-11-06 19:59 ` Andrew Morton
2006-11-06 20:12 ` Christoph Lameter
2006-11-06 20:24 ` Andrew Morton
2006-11-06 20:31 ` Christoph Lameter
2006-11-06 20:42 ` Andrew Morton
2006-11-06 20:58 ` Christoph Lameter
2006-11-06 21:20 ` Andrew Morton
2006-11-06 21:42 ` Christoph Lameter
2006-11-04 1:26 ` Paul Jackson
2006-11-04 1:42 ` Andrew Morton
2006-11-04 10:51 ` Paul Jackson
2006-11-06 16:56 ` Christoph Lameter
2006-11-08 10:21 ` Paul Jackson
2006-11-08 15:18 ` Peter Zijlstra
2006-11-08 17:06 ` Paul Jackson
2006-11-08 17:09 ` Peter Zijlstra [this message]
2006-11-08 17:21 ` Paul Jackson
2006-11-08 17:40 ` Christoph Lameter
2006-12-01 7:51 ` Paul Jackson
2006-12-01 7:59 ` Andrew Morton
2006-12-01 16:27 ` Christoph Lameter
2006-11-04 10:35 ` CTL_UNNUMBERED and killing sys_sysctl Eric W. Biederman
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=1163005750.14238.19.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.