From: Frederic Weisbecker <fweisbec@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux.com>,
Kevin Hilman <khilman@linaro.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Mike Galbraith <bitbucket@online.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH 1/4] workqueue: Create low-level unbound workqueues cpumask
Date: Thu, 1 May 2014 17:01:17 +0200 [thread overview]
Message-ID: <20140501150114.GD25369@localhost.localdomain> (raw)
In-Reply-To: <20140424153716.GG14460@htj.dyndns.org>
On Thu, Apr 24, 2014 at 11:37:16AM -0400, Tejun Heo wrote:
> On Thu, Apr 24, 2014 at 04:37:33PM +0200, Frederic Weisbecker wrote:
> > Create a cpumask that limit the affinity of all unbound workqueues.
> > This cpumask is controlled though a file at the root of the workqueue
> > sysfs directory.
> >
> > It works on a lower-level than the per WQ_SYSFS workqueues cpumask files
> > such that the effective cpumask applied for a given unbound workqueue is
> > the intersection of /sys/devices/virtual/workqueue/$WORKQUEUE/cpumask and
> > the new /sys/devices/virtual/workqueue/cpumask_unbounds file.
>
> Let's drop "_unbounds" postfix and name it just "cpumask". We don't
> apply it to per-cpu workqueues now but that really is an
> implementation detail and later when (and if) we actually distinguish
> per-cpu usages for correctness from for optimization, we may as well
> apply the same cpumask to per-cpu ones too.
Makes sense. But I hope this won't confused too much people. Having
a cpumask file suggests it applies to all of them.
>
> Another thing with naming is that I didn't anticipate having
> attributes at the top directory so the workqueue directories aren't
> namespaced. Maybe we want to namespace top level knobs?
> "system_cpumask" maybe? Any better ideas?
Not sure why you want that. It makes sense on directories grouping
file for different subsystem. But here?
Thanks.
next prev parent reply other threads:[~2014-05-01 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 14:37 [RFC PATCH 0/4] workqueue: Introduce low-level unbound wq sysfs cpumask Frederic Weisbecker
2014-04-24 14:37 ` [PATCH 1/4] workqueue: Create low-level unbound workqueues cpumask Frederic Weisbecker
2014-04-24 15:37 ` Tejun Heo
2014-05-01 15:01 ` Frederic Weisbecker [this message]
2014-05-01 15:02 ` Tejun Heo
2014-05-01 15:09 ` Frederic Weisbecker
2014-05-01 15:13 ` Tejun Heo
2014-04-24 22:42 ` Kevin Hilman
2014-04-24 14:37 ` [PATCH 2/4] workqueue: Split apply attrs code from its locking Frederic Weisbecker
2014-04-24 14:48 ` Tejun Heo
2014-05-01 14:40 ` Frederic Weisbecker
2014-05-01 14:41 ` Tejun Heo
2014-04-24 14:37 ` [PATCH 3/4] workqueue: Allow modifying low level unbound workqueue cpumask Frederic Weisbecker
2014-04-24 15:30 ` Tejun Heo
2014-05-01 14:49 ` Frederic Weisbecker
2014-04-24 14:37 ` [PATCH 4/4] workqueue: Handle ordered workqueues on cpumask_unbounds change Frederic Weisbecker
2014-04-24 15:33 ` Tejun Heo
2014-05-01 14:51 ` Frederic Weisbecker
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=20140501150114.GD25369@localhost.localdomain \
--to=fweisbec@gmail.com \
--cc=bitbucket@online.de \
--cc=cl@linux.com \
--cc=khilman@linaro.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tj@kernel.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