From: Jens Axboe <axboe@fb.com>
To: Josef Bacik <jbacik@fb.com>, <axboe@kernel.dk>,
<linux-block@vger.kernel.org>, <kernel-team@fb.com>
Subject: Re: [PATCH] nbd: use our own workqueue for recv threads
Date: Wed, 1 Feb 2017 17:35:59 -0800 [thread overview]
Message-ID: <bb9bc1c1-c7be-9339-d3c8-a02e79f33db9@fb.com> (raw)
In-Reply-To: <1485983471-3717-1-git-send-email-jbacik@fb.com>
On 02/01/2017 01:11 PM, Josef Bacik wrote:
> Since we are in the memory reclaim path we need our recv work to be on a
> workqueue that has WQ_MEM_RECLAIM set so we can avoid deadlocks. Also
> set WQ_HIGHPRI since we are in the completion path for IO.
Applied for 4.11.
--
Jens Axboe
prev parent reply other threads:[~2017-02-02 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 21:11 [PATCH] nbd: use our own workqueue for recv threads Josef Bacik
2017-02-02 1:35 ` 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=bb9bc1c1-c7be-9339-d3c8-a02e79f33db9@fb.com \
--to=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-block@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