From: Herbert Xu <herbert@gondor.apana.org.au>
To: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Cc: Tadeusz Struk <tadeusz.struk@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Conor McLoughlin <conor.mcloughlin@intel.com>,
Pingchao Yang <pingchao.yang@intel.com>,
Ahsan Atta <ahsan.atta@intel.com>,
John Griffin <john.griffin@intel.com>,
Wu Fengguang <fengguang.wu@intel.com>, Tejun Heo <tj@kernel.org>,
qat-linux@intel.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: qat: Remove deprecated create_workqueue
Date: Mon, 13 Jun 2016 20:29:31 +0800 [thread overview]
Message-ID: <20160613122931.GA8583@gondor.apana.org.au> (raw)
In-Reply-To: <20160607211746.GA17667@Karyakshetra>
On Wed, Jun 08, 2016 at 02:47:47AM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_workqueue().
>
> The workqueue device_reset_wq has workitem &reset_data->reset_work per
> adf_reset_dev_data. The workqueue pf2vf_resp_wq is a workqueue for
> PF2VF responses has workitem &pf2vf_resp->pf2vf_resp_work per pf2vf_resp.
> The workqueue adf_vf_stop_wq is used to call adf_dev_stop()
> asynchronously.
>
> Dedicated workqueues have been used in all cases since the workitems
> on the workqueues are involved in operation of crypto which can be used in
> the IO path which is depended upon during memory reclaim. Hence,
> WQ_MEM_RECLAIM has been set to gurantee forward progress under memory
> pressure.
> Since there are only a fixed number of work items, explicit concurrency
> limit is unnecessary.
>
> Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Patch applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2016-06-13 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 21:17 [PATCH] crypto: qat: Remove deprecated create_workqueue Bhaktipriya Shridhar
2016-06-11 22:46 ` Tejun Heo
2016-06-13 12:29 ` Herbert Xu [this message]
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=20160613122931.GA8583@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=Julia.Lawall@lip6.fr \
--cc=ahsan.atta@intel.com \
--cc=bhaktipriya96@gmail.com \
--cc=conor.mcloughlin@intel.com \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=john.griffin@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pingchao.yang@intel.com \
--cc=qat-linux@intel.com \
--cc=tadeusz.struk@intel.com \
--cc=tj@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).