From: Jens Axboe <axboe@fb.com>
To: Tejun Heo <tj@kernel.org>,
Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
Shaohua Li <shli@kernel.org>,
Eric Wheeler <git@linux.ewheeler.net>,
Zheng Liu <wenqing.lz@taobao.com>, Hannes Reinecke <hare@suse.de>,
Jeff Moyer <jmoyer@redhat.com>, Pekka Enberg <penberg@kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-bcache@vger.kernel.org, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcache: Remove deprecated create_workqueue
Date: Sat, 11 Jun 2016 20:03:33 -0600 [thread overview]
Message-ID: <575CC2F5.2030407@fb.com> (raw)
In-Reply-To: <20160611225202.GD31708@htj.duckdns.org>
On 06/11/2016 04:52 PM, Tejun Heo wrote:
> On Wed, Jun 08, 2016 at 01:57:19AM +0530, Bhaktipriya Shridhar wrote:
>> alloc_workqueue replaces deprecated create_workqueue().
>>
>> Dedicated workqueues have been used since bcache_wq and moving_gc_wq
>> are workqueues for writes and are being used on a memory reclaim path.
>> WQ_MEM_RECLAIM has been set to ensure forward progress under memory
>> pressure.
>> Since there are only a fixed number of work items, explicit concurrency
>> limit is unnecessary here.
>>
>> Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
>
> Acked-by: Tejun Heo <tj@kernel.org>
Added to 4.8, thanks.
--
Jens Axboe
prev parent reply other threads:[~2016-06-12 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 20:27 [PATCH] bcache: Remove deprecated create_workqueue Bhaktipriya Shridhar
2016-06-11 22:52 ` Tejun Heo
2016-06-12 2:03 ` Jens Axboe [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=575CC2F5.2030407@fb.com \
--to=axboe@fb.com \
--cc=bhaktipriya96@gmail.com \
--cc=git@linux.ewheeler.net \
--cc=hare@suse.de \
--cc=jmoyer@redhat.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=shli@kernel.org \
--cc=tj@kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=wenqing.lz@taobao.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;
as well as URLs for NNTP newsgroup(s).