From: Randy Dunlap <rdunlap@infradead.org>
To: "Jens Axboe" <axboe@kernel.dk>,
"André Almeida" <andrealmeid@collabora.com>,
corbet@lwn.net, linux-block@vger.kernel.org,
linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel@collabora.com,
krisman@collabora.com, dongli.zhang@oracle.com
Subject: Re: [PATCH v3] docs: block: Create blk-mq documentation
Date: Fri, 19 Jun 2020 14:09:34 -0700 [thread overview]
Message-ID: <4ff82592-c5cb-bb2a-d298-10a91fb9e69d@infradead.org> (raw)
In-Reply-To: <c2f83c87-f473-4d30-2430-442e957de14f@kernel.dk>
On 6/19/20 1:56 PM, Jens Axboe wrote:
> On 6/19/20 2:01 PM, André Almeida 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 v2:
>> - More fixed typos
>> - Once again, reworked the definition of `blk_mq_hw_ctx` in "Hardware
>> dispatch queues" section
>>
>> Changes from v1:
>> - Fixed typos
>> - Reworked blk_mq_hw_ctx
>>
>> Hello,
>>
>> This commit was tested using "make htmldocs" and the HTML output has
>> been verified.
>>
>> Thanks,
>> André
>> ---
>> Documentation/block/blk-mq.rst | 155 +++++++++++++++++++++++++++++++++
>> Documentation/block/index.rst | 1 +
>> 2 files changed, 156 insertions(+)
>> create mode 100644 Documentation/block/blk-mq.rst
LGTM.
Acked-by: Randy Dunlap <rdunlap@infradead.org>
thanks.
--
~Randy
next prev parent reply other threads:[~2020-06-19 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 20:01 [PATCH v3] docs: block: Create blk-mq documentation André Almeida
2020-06-19 20:56 ` Jens Axboe
2020-06-19 21:09 ` Randy Dunlap [this message]
2020-06-20 0:16 ` André Almeida
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=4ff82592-c5cb-bb2a-d298-10a91fb9e69d@infradead.org \
--to=rdunlap@infradead.org \
--cc=andrealmeid@collabora.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=dongli.zhang@oracle.com \
--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 \
/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).