From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Avoid allocating during interleave from almost full nodes
Date: Thu, 30 Nov 2006 23:51:17 -0800 [thread overview]
Message-ID: <20061130235117.018c3c70.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611060854000.25351@schroedinger.engr.sgi.com>
A month ago, Christoph replied to pj:
>
> On Sat, 4 Nov 2006, Paul Jackson wrote:
>
> > Do you know of any existing counters that we could use like this?
> >
> > Adding a system wide count of pages allocated or scanned, just for
> > these fullnode hint caches, bothers me.
>
> There are already such counters. PGALLOC_* and PGSCAN_*. See
> include/linux/vmstat.h
These counters depend on CONFIG_VM_EVENT_COUNTERS.
The Kconfig comment for CONFIG_VM_EVENT_COUNTERS states:
VM event counters are only needed to for event counts to be
shown. They have no function for the kernel itself. This
option allows the disabling of the VM event counters.
/proc/vmstat will only show page counts.
(By the way - note the "needed to for event" phrasing error.)
The header file, include/linux/vmstat.h, for these counters states:
/*
* Light weight per cpu counter implementation.
*
* Counters should only be incremented and no critical kernel component
* should rely on the counter values.
Both these clearly state that I should not use these counters for real
kernel functions.
If that is so, I should find some other "time base" for the zonelist
caching.
If that is not so, then these comments need updating.
Anybody have any idea which is the case?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-12-01 7:51 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
2006-11-08 17:21 ` Paul Jackson
2006-11-08 17:40 ` Christoph Lameter
2006-12-01 7:51 ` Paul Jackson [this message]
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=20061130235117.018c3c70.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/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