linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Martin Bligh <mbligh@google.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 00/14] Zoned VM counters V5
Date: Wed, 21 Jun 2006 10:21:58 -0700	[thread overview]
Message-ID: <44998036.90704@google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606211012590.20071@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Wed, 21 Jun 2006, Martin Bligh wrote:
> 
> 
>>>Yes later patches also use the counters for other things. Please check out
>>>the patch that uses these for numa counters etc.
>>
>>OK, but looked like the original implementation was sort of tied to
>>zones / the VM, at least in terminology, and code placement. I'll look
>>at it again ...
> 
> 
> Yes it is. This one is useful only for zone related information.
> 
> 
>>>Also smaller counters help keep the pcp structure in one cacheline and
>>>reduces the cache footprint. 
>>
>>Sure, but for a normal sized system, the smaller the per-cpu portion,
>>the more atomic ops you'll end up doing, surely?
> 
> 
> So we now do two atomic ops for every 32 increments (threshold). If we 
> increment the threshhold then we reduce the atomic overhead but this also 
> influences the inaccurary of the global and per zone counter because 
> there is the potential of more counter update deferrals. Keeping the 
> threshold low makes the global and per zone counter more up to date.
> I think 32 is a good compromise.

Ah, makes sense ... so the intent is get an an approximation. If you
want accurate numbers, you still need to walk the per-cpu counters ...
is that too slow for where you're reading it? didn't seem like a
fastpath to me, given that balance_dirty_pages was already ratelimited?
I guess it's still better than what we're doing now though ;-)

M.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-06-21 17:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 15:44 Christoph Lameter
2006-06-21 15:44 ` [PATCH 01/14] Create vmstat.c/.h from page_alloc.c/.h Christoph Lameter
2006-06-21 15:44 ` [PATCH 02/14] Basic ZVC (zoned vm counter) implementation, zoned vm counters: per zone counter functionality Christoph Lameter, Christoph Lameter
     [not found]   ` <20060622041034.84b3c997.akpm@osdl.org>
2006-06-22 14:54     ` [PATCH 02/14] Basic ZVC (zoned vm counter) implementation Christoph Lameter
2006-06-21 15:44 ` [PATCH 03/14] Convert nr_mapped to per zone counter, zoned vm counters: conversion of nr_mapped to per zone counter Christoph Lameter, Christoph Lameter
2006-06-21 15:44 ` [PATCH 04/14] Conversion of nr_pagecache to per zone counter, zoned vm counters: conversion of nr_pagecache " Christoph Lameter, Christoph Lameter
2006-06-21 15:44 ` [PATCH 05/14] Remove NR_FILE_MAPPED from scan control structure, zoned VM stats: Remove nr_mapped from scan control Christoph Lameter, Christoph Lameter
2006-06-21 15:44 ` [PATCH 06/14] Split NR_ANON_PAGES off from NR_FILE_MAPPED, zoned VM stats: Add NR_ANON_PAGES Christoph Lameter, Christoph Lameter
     [not found]   ` <44996F34.1010805@google.com>
2006-06-21 17:01     ` [PATCH 06/14] Split NR_ANON_PAGES off from NR_FILE_MAPPED Christoph Lameter
2006-06-21 15:44 ` [PATCH 07/14] zone_reclaim: remove /proc/sys/vm/zone_reclaim_interval, zoned vm counters: use per zone counters to remove zone_reclaim_interval Christoph Lameter, Christoph Lameter
2006-06-21 15:45 ` [PATCH 08/14] Conversion of nr_slab to per zone counter, zoned vm counters: conversion of nr_slab to per zone counter Christoph Lameter, Christoph Lameter
2006-06-21 15:45 ` [PATCH 09/14] Conversion of nr_pagetables to per zone counter, zoned vm counters: conversion of nr_pagetable " Christoph Lameter, Christoph Lameter
2006-06-21 15:45 ` [PATCH 10/14] Conversion of nr_dirty to per zone counter, zoned vm counters: conversion of nr_dirty " Christoph Lameter, Christoph Lameter
     [not found]   ` <20060624050424.d2160354.akpm@osdl.org>
2006-06-24 18:14     ` [PATCH 10/14] Conversion " Christoph Lameter
2006-06-24 20:53     ` Christoph Lameter
2006-06-21 15:45 ` [PATCH 11/14] Conversion of nr_writeback to per zone counter, zoned vm counters: conversion of nr_writeback " Christoph Lameter, Christoph Lameter
2006-06-21 15:45 ` [PATCH 12/14] Conversion of nr_unstable to per zone counter, zoned vm counters: conversion of nr_unstable " Christoph Lameter, Christoph Lameter
2006-06-21 15:45 ` [PATCH 13/14] Conversion of nr_bounce to per zone counter, zoned vm counters: conversion of nr_bounce " Christoph Lameter, Christoph Lameter
2006-06-21 15:45 ` [PATCH 14/14] Remove useless struct wbs, zoned vm counters: remove useless writeback structure Christoph Lameter, Christoph Lameter
2006-06-21 16:36 ` [PATCH 00/14] Zoned VM counters V5 Martin J. Bligh
2006-06-21 17:06   ` Christoph Lameter
2006-06-21 17:10     ` Martin Bligh
2006-06-21 17:16       ` Christoph Lameter
2006-06-21 17:21         ` Martin Bligh [this message]
2006-06-21 17:29           ` 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=44998036.90704@google.com \
    --to=mbligh@google.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.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