From: Jens Axboe <axboe@kernel.dk>
To: Hillf Danton <hdanton@sina.com>, io-uring@vger.kernel.org
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC PATCH] io-wq: cut busy list off io_wqe
Date: Mon, 23 Dec 2019 08:24:12 -0700 [thread overview]
Message-ID: <c7985b10-52a2-5bb6-d393-f888c4658dd1@kernel.dk> (raw)
In-Reply-To: <20191222144654.5060-1-hdanton@sina.com>
On 12/22/19 7:46 AM, Hillf Danton wrote:
>
> Commit e61df66c69b1 ("io-wq: ensure free/busy list browsing see all
> items") added a list for io workers in addition to the free and busy
> lists, not only making worker walk cleaner but leaving the busy list
> to be at most a nice vase. Time to remove it now.
Thanks, applied.
--
Jens Axboe
parent reply other threads:[~2019-12-23 15:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20191222144654.5060-1-hdanton@sina.com>]
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=c7985b10-52a2-5bb6-d393-f888c4658dd1@kernel.dk \
--to=axboe@kernel.dk \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
/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).