linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Shaohua Li <shli@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch]workqueue: copy attr with all fields.
Date: Wed, 31 Jul 2013 06:27:52 -0400	[thread overview]
Message-ID: <20130731102752.GD2810@htj.dyndns.org> (raw)
In-Reply-To: <20130731013929.GB1504@kernel.org>

Hello,

On Wed, Jul 31, 2013 at 09:39:29AM +0800, Shaohua Li wrote:
> Hmm, I didn't agree it's more confusing to change copy_workqueue_attrs(), the

We're talking past each other.  I'm not saying copy_workqueue_attrs()
shouldn't copy no_numa.  I'm saying get_unbound_pool() should clear
no_numa so that pools don't have random no_numa settings.

> name of the function suggests it is a 'copy'. And clearing no_numa in
> apply_workqueue_attrs() after copy_workqueue_attrs() looks like a hack to me.

Why would apply_workqueue_attrs() modify no_numa when it *is* dealing
with an actual workqueue attr.  I've been talking about
get_unbound_pool() not apply_workqueue_attrs() the whole time.

> But it depends on you, feel free to fix it by yourself.

Please update the patch to add no_numa clearing to get_unbound_pool()
and explain what's going on.

Thanks.

-- 
tejun

  reply	other threads:[~2013-07-31 10:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  6:24 [patch]workqueue: copy attr with all fields Shaohua Li
2013-07-29 11:14 ` Tejun Heo
2013-07-29 12:52   ` Shaohua Li
2013-07-29 15:35     ` Tejun Heo
2013-07-30  5:49       ` Shaohua Li
2013-07-30 14:14         ` Tejun Heo
2013-07-31  1:39           ` Shaohua Li
2013-07-31 10:27             ` Tejun Heo [this message]
2013-08-01  1:56               ` Shaohua Li
2013-08-01 12:35                 ` [PATCH] workqueue: copy workqueue_attrs " Tejun Heo

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=20130731102752.GD2810@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shli@kernel.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;
as well as URLs for NNTP newsgroup(s).