All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peschke <mp3@de.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, akpm@osdl.org,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [RFC] Light weight event counters (V2) instead of page state
Date: Tue, 13 Jun 2006 15:57:10 +0200	[thread overview]
Message-ID: <448EC436.6060008@de.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606121420150.21448@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> We would like to have some solution that reduces the
> overhead for these counters. VM counters currently require interrupt disabling
> in order to work. Maybe we can avoid that by using the local_t which provides
> an increment operation that is not atomic vs other processors but atomic vs
> interrupts on this same processor.
 >
 > The patchset also adds an off switch for embedded systems that allows a
 > building of linux kernels without these counters.

Did you consider using the statistics infrastructure available in -mm?
(lib/statistic.c, include/linux/statistic.h, Documentation/statistics.txt)

It's a ready-to-use statistics library that comes with similar characteristics
as you have described above.

 > The remaining counters in page_state after the zoned VM counter patch has
 > been applied are all just for show in /proc/vmstat.  They have no essential
 > function for the VM.

To me that looks like a good application for the statistics infrastructure,
which shows statistics through debugfs instead of procfs. Btw., it completely
unburdens exploiting kernel code from the delivery of statistics to users.

	Martin


  reply	other threads:[~2006-06-13 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12 21:21 [RFC] Light weight event counters (V2) instead of page state Christoph Lameter
2006-06-13 13:57 ` Martin Peschke [this message]
2006-06-13 15:23   ` 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=448EC436.6060008@de.ibm.com \
    --to=mp3@de.ibm.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.