From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Dave Jones <davej@redhat.com>
Cc: Nate Diller <nate.diller@gmail.com>,
Andrew Morton <akpm@osdl.org>, Jens Axboe <axboe@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -mm] [1/2] Remove Deadline I/O scheduler
Date: Thu, 3 Aug 2006 16:37:20 -0700 [thread overview]
Message-ID: <20060803163720.e9ba5f3a.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060803233048.GA7265@redhat.com>
On Thu, 3 Aug 2006 19:30:48 -0400 Dave Jones wrote:
> On Thu, Aug 03, 2006 at 03:57:32PM -0700, 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.
>
> Its somewhat hard for folks to offer comparative benchmarks when you
> remove something. Without any numbers at all showing why your elevator
> is superior, removing anything seems very premature.
>
> I'm also not convinced that removing an elevator at all is a good idea,
> as it'll cause regressions for anyone who has boot scripts that set
> certain mounts to use deadline for eg.
Shouldn't the usual feature-removal in N months be used here?
if at all.
(Documentation/feature-removal-schedule.txt)
---
~Randy
next prev parent reply other threads:[~2006-08-03 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 22:57 Nate Diller
2006-08-03 23:17 ` Randy.Dunlap
2006-08-03 23:30 ` Dave Jones
2006-08-03 23:37 ` Randy.Dunlap [this message]
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
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=20060803163720.e9ba5f3a.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=davej@redhat.com \
--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
all inboxes | Powered by JetHome®