From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: miklos@szeredi.hu, akpm@linux-foundation.org, neilb@suse.de,
dgc@sgi.com, tomoki.sekiyama.qu@hitachi.com,
a.p.zijlstra@chello.nl, nikita@clusterfs.com,
trond.myklebust@fys.uio.no, yingchao.zhou@gmail.com
Subject: [PATCH 03/12] lib: dampen the percpu_counter FBC_BATCH
Date: Tue, 17 Apr 2007 09:10:49 +0200 [thread overview]
Message-ID: <20070417071702.933410506@chello.nl> (raw)
In-Reply-To: <20070417071046.318415445@chello.nl>
[-- Attachment #1: percpu_counter_batch.patch --]
[-- Type: text/plain, Size: 1174 bytes --]
With the current logic the percpu_counter's accuracy delta is quadric
wrt the number of cpus in the system, reduce this to O(n ln n).
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
include/linux/percpu_counter.h | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
Index: linux-2.6-mm/include/linux/percpu_counter.h
===================================================================
--- linux-2.6-mm.orig/include/linux/percpu_counter.h
+++ linux-2.6-mm/include/linux/percpu_counter.h
@@ -11,6 +11,7 @@
#include <linux/threads.h>
#include <linux/percpu.h>
#include <linux/types.h>
+#include <linux/log2.h>
#ifdef CONFIG_SMP
@@ -20,11 +21,7 @@ struct percpu_counter {
s32 *counters;
};
-#if NR_CPUS >= 16
-#define FBC_BATCH (NR_CPUS*2)
-#else
-#define FBC_BATCH (NR_CPUS*4)
-#endif
+#define FBC_BATCH (8*ilog2(NR_CPUS))
static inline void percpu_counter_init(struct percpu_counter *fbc, s64 amount)
{
--
--
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>
next prev parent reply other threads:[~2007-04-17 7:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 7:10 [PATCH 00/12] per device dirty throttling -v4 Peter Zijlstra
2007-04-17 7:10 ` [PATCH 01/12] revert per-backing_dev-dirty-and-writeback-page-accounting Peter Zijlstra
2007-04-17 7:10 ` [PATCH 02/12] nfs: remove congestion_end() Peter Zijlstra
2007-04-17 7:10 ` Peter Zijlstra [this message]
2007-04-17 7:10 ` [PATCH 04/12] lib: percpu_counter_mod64 Peter Zijlstra
2007-04-17 7:10 ` [PATCH 05/12] mm: bdi init hooks Peter Zijlstra
2007-04-17 7:10 ` [PATCH 06/12] mm: scalable bdi statistics counters Peter Zijlstra
2007-04-17 7:10 ` [PATCH 07/12] mm: count dirty pages per BDI Peter Zijlstra
2007-04-17 7:10 ` [PATCH 08/12] mm: count writeback " Peter Zijlstra
2007-04-17 7:10 ` [PATCH 09/12] mm: count unstable " Peter Zijlstra
2007-04-19 17:44 ` Miklos Szeredi
2007-04-19 18:12 ` Peter Zijlstra
2007-04-19 18:46 ` Peter Zijlstra
2007-04-19 19:00 ` Peter Zijlstra
2007-04-19 19:20 ` Miklos Szeredi
2007-04-19 19:23 ` Peter Zijlstra
2007-04-17 7:10 ` [PATCH 10/12] mm: expose BDI statistics in sysfs Peter Zijlstra
2007-04-17 7:10 ` [PATCH 11/12] mm: per device dirty threshold Peter Zijlstra
2007-04-19 17:49 ` Miklos Szeredi
2007-04-19 18:04 ` Peter Zijlstra
2007-04-17 7:10 ` [PATCH 12/12] debug: expose BDI statistics in sysfs Peter Zijlstra
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=20070417071702.933410506@chello.nl \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miklos@szeredi.hu \
--cc=neilb@suse.de \
--cc=nikita@clusterfs.com \
--cc=tomoki.sekiyama.qu@hitachi.com \
--cc=trond.myklebust@fys.uio.no \
--cc=yingchao.zhou@gmail.com \
/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