From: Keith Owens <kaos@sgi.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, Hugh Dickins <hugh@veritas.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
linux-mm@kvack.org, linux-ia64@vger.kernel.org,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: [RFC 1/3] Framework for accurate node based statistics
Date: Wed, 07 Dec 2005 16:50:52 +1100 [thread overview]
Message-ID: <9353.1133934652@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 06 Dec 2005 14:52:33 -0800." <Pine.LNX.4.62.0512061447590.20377@schroedinger.engr.sgi.com>
On Tue, 6 Dec 2005 14:52:33 -0800 (PST),
Christoph Lameter <clameter@engr.sgi.com> wrote:
>+DEFINE_PER_CPU(local_t [MAX_NUMNODES][NR_STAT_ITEMS], vm_stat_diff);
How big is that array going to get? The total per cpu data area is
limited to 64K on IA64 and we already use at least 34K.
next prev parent reply other threads:[~2005-12-07 5:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 18:28 [RFC 1/3] Framework for accurate node based statistics Christoph Lameter
2005-12-06 18:28 ` [RFC 2/3] Make nr_mapped a per node counter Christoph Lameter
2005-12-06 23:05 ` Nick Piggin
2005-12-06 18:28 ` [RFC 3/3] Make nr_pagecache " Christoph Lameter
2005-12-06 18:35 ` [RFC 1/3] Framework for accurate node based statistics Andi Kleen
2005-12-06 19:08 ` Christoph Lameter
2005-12-06 19:26 ` Andi Kleen
2005-12-06 19:36 ` Christoph Lameter
2005-12-06 20:06 ` Andi Kleen
2005-12-06 22:52 ` Christoph Lameter
2005-12-07 5:50 ` Keith Owens [this message]
2005-12-07 18:24 ` Christoph Lameter
2005-12-06 23:08 ` Nick Piggin
2005-12-06 23:37 ` Christoph Lameter
2005-12-06 23:40 ` Christoph Lameter
2005-12-07 6:44 ` Nick Piggin
2005-12-07 18:27 ` Christoph Lameter
2005-12-07 22:59 ` Nick Piggin
2005-12-08 0:02 ` Christoph Lameter
2005-12-08 0:13 ` Nick Piggin
2005-12-08 0:35 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2005-12-07 18:39 Luck, Tony
2005-12-07 18:47 ` 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=9353.1133934652@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=ak@suse.de \
--cc=clameter@engr.sgi.com \
--cc=hugh@veritas.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--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