From: Jens Axboe <axboe@kernel.dk>
To: "Randy Dunlap" <rdunlap@infradead.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"André Almeida" <andrealmeid@collabora.com>
Cc: linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com,
krisman@collabora.com
Subject: Re: [PATCH v2] docs: block: Create blk-mq documentation
Date: Fri, 19 Jun 2020 14:49:27 -0600 [thread overview]
Message-ID: <a9b6447f-1b24-5f71-3661-c6ea5fe8ba6e@kernel.dk> (raw)
In-Reply-To: <cdab3be8-0d39-5085-34b5-7bf11cc7fb60@infradead.org>
On 6/19/20 1:47 PM, Randy Dunlap wrote:
> On 6/19/20 12:45 PM, Jonathan Corbet wrote:
>> On Fri, 5 Jun 2020 14:55:36 -0300
>> André Almeida <andrealmeid@collabora.com> wrote:
>>
>>> Create a documentation providing a background and explanation around the
>>> operation of the Multi-Queue Block IO Queueing Mechanism (blk-mq).
>>>
>>> The reference for writing this documentation was the source code and
>>> "Linux Block IO: Introducing Multi-queue SSD Access on Multi-core
>>> Systems", by Axboe et al.
>>>
>>> Signed-off-by: André Almeida <andrealmeid@collabora.com>
>>> ---
>>> Changes from v1:
>>> - Fixed typos
>>> - Reworked blk_mq_hw_ctx
>>
>> Jens, what's your pleasure on this one? Should I take it, or do you want
>> it...?
>
> I wouldn't mind seeing a v3.
Agree - Jon, I'd be happy with you taking it once a v3 is posted with the
remaining issues ironed out.
--
Jens Axboe
next prev parent reply other threads:[~2020-06-19 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 17:55 [PATCH v2] docs: block: Create blk-mq documentation André Almeida
2020-06-05 23:45 ` Dongli Zhang
2020-06-16 13:54 ` André Almeida
2020-06-16 0:15 ` Randy Dunlap
2020-06-16 13:59 ` André Almeida
2020-06-19 19:45 ` Jonathan Corbet
2020-06-19 19:47 ` Randy Dunlap
2020-06-19 20:49 ` Jens Axboe [this message]
2020-06-19 20:51 ` André Almeida
2020-06-19 20:56 ` Jens Axboe
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=a9b6447f-1b24-5f71-3661-c6ea5fe8ba6e@kernel.dk \
--to=axboe@kernel.dk \
--cc=andrealmeid@collabora.com \
--cc=corbet@lwn.net \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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).