From: Christoph Lameter <cl@linux.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Al Viro <viro@zeniv.linux.org.uk>,
Dave Hansen <dave.hansen@intel.com>,
Andi Kleen <ak@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 1/2] Make the batch size of the percpu_counter configurable
Date: Tue, 30 Apr 2013 20:50:26 +0000 [thread overview]
Message-ID: <0000013e5cb5ec6a-04ce1f4a-c4b9-430f-8235-69e92482faad-000000@email.amazonses.com> (raw)
In-Reply-To: <1367348457.27102.197.camel@schen9-DESK>
On Tue, 30 Apr 2013, Tim Chen wrote:
> Will it be acceptable if I make the per cpu counter list under
> CONFIG_CPU_HOTPLUG default? I will need the list to go through all
> counters to update the batch value sizes. The alternative will be to
> make the configurable batch option only available under
> CONFIG_HOTPLUG_CPU.
Make the list default. Could be useful elsewhere.
--
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:[~2013-04-30 20:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 17:12 Tim Chen
2013-04-29 17:12 ` [PATCH 2/2] Make batch size for memory accounting configured according to size of memory Tim Chen
2013-05-01 5:09 ` Ric Mason
2013-05-01 16:07 ` Tim Chen
2013-04-30 13:32 ` [PATCH 1/2] Make the batch size of the percpu_counter configurable Christoph Lameter
2013-04-30 16:23 ` Tim Chen
2013-04-30 17:28 ` Christoph Lameter
2013-04-30 17:48 ` Tim Chen
2013-04-30 17:53 ` Christoph Lameter
2013-04-30 17:55 ` Tim Chen
2013-04-30 18:27 ` Christoph Lameter
2013-04-30 19:00 ` Tim Chen
2013-04-30 19:04 ` Tejun Heo
2013-04-30 20:50 ` Christoph Lameter [this message]
2013-04-30 17:34 ` Andi Kleen
2013-04-30 18:10 ` Eric Dumazet
2013-04-30 18:28 ` Tim Chen
2013-05-01 4:52 ` Simon Jeons
2013-05-01 15:53 ` Tim Chen
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=0000013e5cb5ec6a-04ce1f4a-c4b9-430f-8235-69e92482faad-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tim.c.chen@linux.intel.com \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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