From: Hannes Reinecke <hare@suse.de>
To: Bart Van Assche <bart.vanassche@sandisk.com>, Jens Axboe <axboe@fb.com>
Cc: Christoph Hellwig <hch@lst.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Block layer state diagrams
Date: Thu, 27 Oct 2016 07:45:35 +0200 [thread overview]
Message-ID: <865bd65b-b26e-d8e0-1b0e-ad715ea4d8d2@suse.de> (raw)
In-Reply-To: <0213e715-5d87-1110-45d5-ed48f8837842@sandisk.com>
On 10/26/2016 10:21 PM, Bart Van Assche wrote:
> Hello Jens,
>
> Some time ago I created the attached state diagrams for myself to avoid
> that I would have to reread the entire block layer core source code if
> it has been a while since I had a look at it. Do you think it would be
> useful to add these diagrams somewhere in the Documentation directory?
>
Can you add a step for the mapping between software and
hardware queues?
Also the actual submission to the LLDD (in step 'executing') could do
with a bit more emphasis.
And maybe the fontsize could be a tad smaller; currently it's hard to
figure out which label goes where, expecially in the bottom half.
Otherwise looking good.
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-10-27 5:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 20:21 Block layer state diagrams Bart Van Assche
2016-10-27 5:45 ` Hannes Reinecke [this message]
2016-10-27 22:37 ` Bart Van Assche
2016-10-28 15:45 ` Jens Axboe
2016-10-28 16:06 ` Bart Van Assche
2016-10-28 16:24 ` 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=865bd65b-b26e-d8e0-1b0e-ad715ea4d8d2@suse.de \
--to=hare@suse.de \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=hch@lst.de \
--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