From: Matthew Wilcox <matthew@wil.cx>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Christoph Lameter <clameter@sgi.com>,
Hugh Dickins <hugh@veritas.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-mm@kvack.org, linux-ia64@vger.kernel.org
Subject: Re: removing mm->rss and mm->anon_rss from kernel?
Date: Tue, 09 Nov 2004 12:10:37 +0000 [thread overview]
Message-ID: <20041109121037.GQ24690@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <41902E14.4080904@yahoo.com.au>
On Tue, Nov 09, 2004 at 01:40:20PM +1100, Nick Piggin wrote:
> I wonder if a per process flag or something could be used to turn off
> the statistics counters? I guess statistics could still be gathered for
> that process by using your lazy counting functions, Christoph.
I don't get it. It seems to me that any process that's going to
experience problems with these statistics counters is going to be
precisely the one that you want the statistics for! What was the problem
with per-cpu counters again?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-11-09 12:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4189EC67.40601@yahoo.com.au>
[not found] ` <Pine.LNX.4.58.0411040820250.8211@schroedinger.engr.sgi.com>
[not found] ` <418AD329.3000609@yahoo.com.au>
[not found] ` <Pine.LNX.4.58.0411041733270.11583@schroedinger.engr.sgi.com>
[not found] ` <418AE0F0.5050908@yahoo.com.au>
[not found] ` <418AE9BB.1000602@yahoo.com.au>
[not found] ` <1099622957.29587.101.camel@gaston>
[not found] ` <418C55A7.9030100@yahoo.com.au>
2004-11-06 9:28 ` removing mm->rss and mm->anon_rss from kernel? Christoph Lameter
[not found] ` <204290000.1099754257@[10.10.2.4]>
2004-11-06 16:19 ` Christoph Lameter
2004-11-06 20:05 ` William Lee Irwin III
2004-11-07 16:11 ` Martin J. Bligh
2004-11-07 18:25 ` Matthew Wilcox
2004-11-08 12:43 ` Jesse Barnes
2004-11-08 15:26 ` Andi Kleen
2004-11-08 16:07 ` Christoph Lameter
2004-11-08 16:04 ` Christoph Lameter
2004-11-08 16:12 ` Anton Blanchard
2004-11-08 16:14 ` Martin J. Bligh
2004-11-08 16:25 ` Christoph Lameter
2004-11-08 16:30 ` Erich Focht
2004-11-08 16:57 ` Diego Calleja
2004-11-08 17:26 ` Erich Focht
2004-11-10 11:57 ` Magnus Damm
2004-11-06 20:51 ` Rik van Riel
2004-11-08 15:47 ` Russ Anderson
2004-11-08 16:08 ` Martin J. Bligh
2004-11-10 4:52 ` Nick Piggin
2004-11-10 17:30 ` Robin Holt
2004-11-10 18:50 ` Ray Bryant
2004-11-12 23:45 ` Ray Bryant
2004-11-13 0:05 ` Steve Neuner
2004-11-08 16:35 ` Rik van Riel
2004-11-08 16:56 ` Hugh Dickins
2004-11-08 17:01 ` Christoph Lameter
2004-11-09 2:40 ` Nick Piggin
2004-11-09 12:10 ` Matthew Wilcox [this message]
2004-11-10 0:48 ` Nick Piggin
2004-11-12 0:38 ` Christoph Lameter
2004-11-12 12:50 ` Robin Holt
2004-11-12 15:02 ` 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=20041109121037.GQ24690@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=benh@kernel.crashing.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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