Re: Linux I/O stack design question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jeff,

On Don, 2011-09-01 at 10:19 -0400, Jeff Moyer wrote:
> Werner Fischer <devlists@xxxxxxxx> writes:
> > http://www.thomas-krenn.com/de/wikiDE/images/0/07/Linux-IO-Stack.png
> > Is this diagram correct or are there any errors in there?
> 
> That's a nice diagram.  :)
Thanks! ;-)

> A few of things of note:
> 1) O_DIRECT I/O can bypass the page cache
you are right, I'll add it.

> 2) request-based dm targets sit below the I/O scheduler (currently, that
>    just means dm-multipath)
Thanks, I'll correct this.

> 3) the fusion IO device driver can hook itself in where you put it, or
>    also up above the I/O scheduler (based on a module load option).
Oh wow, that sounds interesting. Does this mean that in this case (IO
device driver above the I/O scheduler) simply no I/O scheduler is used?

> 4) not sure if you want to cover I/O directly to the device (no file
>    system involved)
Yea, that sound reasonable. I'll add it.

So thanks a lot for your valuable feedback.
I will update the diagram according to your hints and let you know then.

Once the diagram is in a state that seems reasonable, I'll add it to
Wikipedia commons under some open license and include it in articles
where it makes sense (e.g.
http://en.wikipedia.org/wiki/Deadline_scheduler and so on)

Regards,
Werner


--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux