From: "Georg Schönberger" <gschoenberger@thomas-krenn.com>
To: fio@vger.kernel.org
Subject: IO Scheduler Diagrams
Date: Fri, 5 Oct 2012 11:41:56 +0200 (CEST) [thread overview]
Message-ID: <1336570145.255301.1349430116859.JavaMail.root@thomas-krenn.com> (raw)
In-Reply-To: <1756305799.255171.1349429682456.JavaMail.root@thomas-krenn.com>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
Hello,
this topic is not directly connected to Fio but nevertheless reasonable for all Fio Users.
I am currently working on IO Scheduler Diagrams explaining how they process IO requests.
Attached you find my first draft, I've already had some input from Christoph Hellwig. I would be happy
if I get more feedback as I am not sure if everything is correct, especially with CFQ I had some problems drawing it.
-Georg
[-- Attachment #2: io_scheduler_diagram.png --]
[-- Type: image/png, Size: 92699 bytes --]
next parent reply other threads:[~2012-10-05 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1756305799.255171.1349429682456.JavaMail.root@thomas-krenn.com>
2012-10-05 9:41 ` Georg Schönberger [this message]
2012-10-05 11:40 ` IO Scheduler Diagrams 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=1336570145.255301.1349430116859.JavaMail.root@thomas-krenn.com \
--to=gschoenberger@thomas-krenn.com \
--cc=fio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.