public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFT] simple deadline I/O scheduler
Date: Tue, 8 Jan 2002 07:43:50 +0100	[thread overview]
Message-ID: <20020108074350.Q1755@suse.de> (raw)
In-Reply-To: <20020104094334.N8673@suse.de> <20020105133800.A37@toy.ucw.cz>
In-Reply-To: <20020105133800.A37@toy.ucw.cz>

On Sat, Jan 05 2002, Pavel Machek wrote:
> Hi!
> 
> > I've played around with implementing an I/O scheduler that _tries_ to
> > start request within a given time limit. Note that it makes no
> > guarentees of any sort, it's simply a "how does this work in real life"
> > sort of thing. It's main use is actually to properly extend the i/o
> > scheduler / elevator api to be able to implement more advanced
> > schedulers (eg cello).
> 
> Would it be possible to introduce concept of I/O priority? I.e. I want 
> updatedb not to load disk if I need it for something else?

I've been toying with equal i/o distribution between the processes in
the system, but it isn't done yet. I know Arjan is working on a priority
scheduler, too. So something is bound to materialize sooner or later :)

-- 
Jens Axboe


  parent reply	other threads:[~2002-01-08  6:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04  8:43 [PATCH][RFT] simple deadline I/O scheduler Jens Axboe
2002-01-04  9:21 ` Jens Axboe
2002-01-04 10:51   ` Jens Axboe
2002-01-05 13:38 ` Pavel Machek
2002-01-07 19:31   ` Mark Hahn
2002-01-07 19:57     ` Rik van Riel
2002-01-08  6:43   ` Jens Axboe [this message]
2002-03-13 13:33 ` Daniel Phillips
2002-03-14  7:32   ` Jens Axboe
2002-03-14 15:51     ` Daniel Phillips
2002-03-15 10:57       ` 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=20020108074350.Q1755@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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