From: Christoph Lameter <cl@gentwo.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Gilad Ben-Yossef <gilad@benyossef.com>,
Thomas Gleixner <tglx@linutronix.de>, Tejun Heo <tj@kernel.org>,
John Stultz <johnstul@us.ibm.com>,
Mike Frysinger <vapier@gentoo.org>,
Minchan Kim <minchan.kim@gmail.com>,
Hakan Akkan <hakanakkan@gmail.com>,
Max Krasnyansky <maxk@qualcomm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
hughd@google.com, viresh.kumar@linaro.org, hpa@zytor.com,
mingo@kernel.org, peterz@infradead.org
Subject: Re: vmstat: On demand vmstat workers V5
Date: Thu, 29 May 2014 09:07:44 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1405290902180.11514@gentwo.org> (raw)
In-Reply-To: <20140529003609.GG6507@localhost.localdomain>
On Thu, 29 May 2014, Frederic Weisbecker wrote:
> The cpumasks in cpu.c are special as they are the base of the cpumask_var_t
> definition. They are necessary to define nr_cpu_bits which is the base of
> cpumask_var_t allocations. As such they must stay lower level and defined
> on top of NR_CPUS.
>
> But most other cases don't need that huge static bitmap. I actually haven't
> seen any other struct cpumask than isn't based on cpumask_var_t.
Well yes and I am tying directly into that scheme there in cpu.c to
display the active vmstat threads in sysfs. so its the same.
> Please post it on a new thread so it gets noticed by others.
Ok. Will do when we got agreement on the cpumask issue.
I would like to have some way to display the activities on cpus in /sysfs
like I have done here with the active vmstat workers.
What I think we need is display cpumasks for
1. Cpus where the tick is currently off
2. Cpus that have dynticks enabled.
3. Cpus that are idle
4. Cpus that are used for RCU.
--
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:[~2014-05-29 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 18:18 Christoph Lameter
2014-05-13 15:24 ` Thomas Gleixner
2014-05-14 16:07 ` Christoph Lameter
2014-05-14 23:15 ` Thomas Gleixner
2014-05-27 20:07 ` Christoph Lameter
2014-05-28 15:21 ` Frederic Weisbecker
2014-05-28 16:19 ` Christoph Lameter
2014-05-29 0:36 ` Frederic Weisbecker
2014-05-29 14:07 ` Christoph Lameter [this message]
2014-05-29 14:26 ` Frederic Weisbecker
2014-05-29 16:24 ` Christoph Lameter
2014-05-29 16:40 ` Paul E. McKenney
2014-05-29 16:29 ` Paul E. McKenney
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=alpine.DEB.2.10.1405290902180.11514@gentwo.org \
--to=cl@gentwo.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=gilad@benyossef.com \
--cc=hakanakkan@gmail.com \
--cc=hpa@zytor.com \
--cc=hughd@google.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maxk@qualcomm.com \
--cc=minchan.kim@gmail.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vapier@gentoo.org \
--cc=viresh.kumar@linaro.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