All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Martin Steigerwald <ms@teamix.de>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Aaron Carroll <aaronc@gelato.unsw.edu.au>
Subject: Re: Documentation on CFQ iosched parameters
Date: Tue, 23 Sep 2008 11:32:18 +0200	[thread overview]
Message-ID: <20080923093218.GY26460@kernel.dk> (raw)
In-Reply-To: <200809231126.51902.ms@teamix.de>

On Tue, Sep 23 2008, Martin Steigerwald wrote:
> Am Dienstag, 23. September 2008 schrieb Aaron Carroll:
> > Martin Steigerwald wrote:
> > > Hi!
> > >
> > > I am searching documentation about CFQ io scheduler. I can't find it in
> > > linux 2.6.26 Documentation directory.
> > >
> > > I found about these in german[1]:
> > >
> > > back_seek_max:16384
> > > back_seek_penalty:2
> > > fifo_expire_async:250
> > > fifo_expire_sync:123
> > > quantum:4
> > >
> > > But I am completely missing about these:
> > >
> > > slice_async:40
> >
> > Base length of an asynchronous queue timeslice (that is, how long the
> > queue has to dispatch requests each round).  The actual timeslice
> > length is scaled by the I/O priority.
> 
> [...]
> 
> Thanks. As I do not find documentation about CFQ at all, I think I need to 
> create a new file from scratch... how about 
> Documentation/block/cfq-iosched.txt?

That would be great!

> For that I need some more information about CFQ. I found the following 
> resources:
> 
> - CFQ V3 aka CFQ TS: http://lwn.net/Articles/143474/, 
> http://lwn.net/Articles/114770/ and posts by Jens, 
> http://lwn.net/Articles/113869/
> 
> - CFQ V2: Post by Jens, http://lwn.net/Articles/101029/
> 
> - CFQ: Post by Jens, http://lwn.net/Articles/22429/

You can mention the links for v1 and v2, but as they have even little
historic relevance, don't spend more time on that.

> - Documentation/block/as-iosched.txt / deadline-iosched.txt (as for how an IO 
> scheduler can be documented)
> 
> Would that be what I should read in order to write such an documentation? 

Yes

> How about the relevance of CFQ and CFQ v2 stuff? What of it would be good to 
> mention? I would like to limit documentation to what is still relevant for 
> the current implementation of the IO scheduler. Should I mention its 
> inheritance from SFQ - maybe in a small introduction and historic overview?

Even the very first CFQ posted used per-process queues, so there's
really very little inheritance from SFQ at all. So I don't think it's
particularly interesting to mention. But if you want, go ahead :-)


-- 
Jens Axboe


      reply	other threads:[~2008-09-23  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 15:15 Documentation on CFQ iosched parameters Martin Steigerwald
2008-09-23  3:15 ` Aaron Carroll
2008-09-23  9:00   ` Jens Axboe
2008-09-23  9:26   ` Martin Steigerwald
2008-09-23  9:32     ` Jens Axboe [this message]

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=20080923093218.GY26460@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=aaronc@gelato.unsw.edu.au \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ms@teamix.de \
    /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.