From: Tejun Heo <tj@kernel.org>
To: Peter Chang <dpf@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: PATCH: platforms: avoid queuing work if possible
Date: Fri, 31 Jan 2014 07:00:15 -0500 [thread overview]
Message-ID: <20140131120015.GE26148@htj.dyndns.org> (raw)
In-Reply-To: <20140131115340.GD26148@htj.dyndns.org>
On Fri, Jan 31, 2014 at 06:53:40AM -0500, Tejun Heo wrote:
> The patch description doesn't describe the reasons for the change at
> all. What issues have you encountered? What are you trying to
> achieve?
Okay, is it that on NUMA configurations the probing ends up being
bounced through work_on_cpu(), so tracking whether "async" was used
doesn't work making module probing finish before async probing is
complete? If that's the case, wouldn't a more generic workaround be
handling that in work_on_cpu()? You can change work_for_cpu_fn() to
clear ASYNC_USED before invoking the function and transfer the bit to
struct work_for_cpu so that work_on_cpu() can again transfer it to the
calling task.
Thanks.
--
tejun
next prev parent reply other threads:[~2014-01-31 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 1:24 PATCH: platforms: avoid queuing work if possible Peter Chang
2014-01-31 11:53 ` Tejun Heo
2014-01-31 12:00 ` Tejun Heo [this message]
2014-02-05 4:13 ` Peter Chang
2014-02-10 22:41 ` 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=20140131120015.GE26148@htj.dyndns.org \
--to=tj@kernel.org \
--cc=dpf@google.com \
--cc=linux-pci@vger.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).