public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Aaron Carroll <aaronc@gelato.unsw.edu.au>
Cc: Martin Steigerwald <ms@teamix.de>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Documentation on CFQ iosched parameters
Date: Tue, 23 Sep 2008 11:00:29 +0200	[thread overview]
Message-ID: <20080923090029.GV26460@kernel.dk> (raw)
In-Reply-To: <48D85F49.4080001@gelato.unsw.edu.au>

On Tue, Sep 23 2008, Aaron Carroll wrote:
> 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.
> 
> >slice_async_rq:2
> 
> The base number of requests per round for asynchronous queues.  Like
> slice_async, the actual maximum is a function of slice_async_rq and I/O
> priority.
> 
> >slice_idle:6
> 
> How long to wait for processes to produce more I/O before switching
> queues. This is for anticipation of sequential I/O, and more even disk
> time distribution for processes doing back to back synchronous I/Os.
> 
> >slice_sync:100
> 
> Same as slice_async, but for synchronous requests.

Nothing further to add, Aaron nailed them.

-- 
Jens Axboe


  reply	other threads:[~2008-09-23  9:00 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 [this message]
2008-09-23  9:26   ` Martin Steigerwald
2008-09-23  9:32     ` 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=20080923090029.GV26460@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox