From: Jens Axboe <axboe@suse.de>
To: Nate Diller <nate.diller@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -mm] [1/2] Remove Deadline I/O scheduler
Date: Fri, 4 Aug 2006 06:24:55 +0200 [thread overview]
Message-ID: <20060804042454.GN16754@suse.de> (raw)
In-Reply-To: <5c49b0ed0608031557n405196ack3fa2024aae8a9475@mail.gmail.com>
On Thu, Aug 03 2006, Nate Diller wrote:
> This patch removes the Deadline I/O scheduler. Performance-wise, it
> should be superceeded by the Elevator I/O scheduler in the following
> patch. I would be very ineterested in hearing about any workloads or
> benchmarks where Deadline is a substantial improvement over Elevator,
> in throughput, fairness, latency, anything.
Strong NAK. deadline is a simple, working scheduler. Why on earth would
you want to remove it?
--
Jens Axboe
prev parent reply other threads:[~2006-08-04 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 22:57 [PATCH -mm] [1/2] Remove Deadline I/O scheduler Nate Diller
2006-08-03 23:17 ` Randy.Dunlap
2006-08-03 23:30 ` Dave Jones
2006-08-03 23:37 ` Randy.Dunlap
2006-08-03 23:46 ` Adrian Bunk
2006-08-04 0:15 ` Nate Diller
2006-08-04 1:03 ` Andrew Morton
2006-08-04 4:24 ` 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=20060804042454.GN16754@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nate.diller@gmail.com \
/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