From: Tejun Heo <tj@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: NeilBrown <neilb@suse.com>, Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
lustre <lustre-devel@lists.lustre.org>,
Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: [PATCH 3/4] staging: lustre: lnet: convert selftest to use workqueues
Date: Mon, 8 Jan 2018 06:55:27 -0800 [thread overview]
Message-ID: <20180108145527.GT3668920@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180108144558.GA6826@kroah.com>
Hello, Greg.
On Mon, Jan 08, 2018 at 03:45:58PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Dec 18, 2017 at 12:25:19PM +1100, NeilBrown wrote:
> > Instead of the cfs workitem library, use workqueues.
> >
> > As lnet wants to provide a cpu mask of allowed cpus, it
> > needs to be a WQ_UNBOUND work queue so that tasks can
> > run on cpus other than where they were submitted.
>
> This patch doesn't apply to my tree :(
>
> > apply_workqueue_atts needs to be exported for lustre to use it.
>
> That feels really odd, why is lustre so "special" that the normal
> workqueue api doesn't work properly for it?
>
> I've dropped this, and the next patch, from my queue now. Please fix up
> and resend and justify why lustre is so odd :)
The workqueue attrs interface is relatively new and just hasn't had
internal module users. It's not necessarily odd to want to use them
from modules. I'll be happy to ack patches which add
EXPORT_SYMBOL_GPL() on them.
Thanks.
--
tejun
next prev parent reply other threads:[~2018-01-08 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 1:25 [PATCH SERIES 3: 0/4] staging:lustre: remove workitem code NeilBrown
2017-12-18 1:25 ` [PATCH 1/4] staging: lustre: libcfs: use a workqueue for rehash work NeilBrown
2017-12-18 1:25 ` [PATCH 3/4] staging: lustre: lnet: convert selftest to use workqueues NeilBrown
2018-01-08 14:45 ` Greg Kroah-Hartman
2018-01-08 14:55 ` Tejun Heo [this message]
2018-01-08 15:06 ` Greg Kroah-Hartman
2018-01-09 1:29 ` NeilBrown
2017-12-18 1:25 ` [PATCH 4/4] staging: lustre: libcfs: remove workitem code NeilBrown
2017-12-18 1:25 ` [PATCH 2/4] staging: lustre: libcfs: remove wi_data from cfs_workitem NeilBrown
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=20180108145527.GT3668920@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=andreas.dilger@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=neilb@suse.com \
--cc=oleg.drokin@intel.com \
/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