linux-kernel - Re: [PATCH -mm] [1/2] Remove Deadline I/O scheduler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060803163720.e9ba5f3a.rdunlap@xenotime.net>
Date:	Thu, 3 Aug 2006 16:37:20 -0700
From:	"Randy.Dunlap" <rdunlap@...otime.net>
To:	Dave Jones <davej@...hat.com>
Cc:	Nate Diller <nate.diller@...il.com>, Andrew Morton <akpm@...l.org>,
	Jens Axboe <axboe@...e.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -mm] [1/2] Remove Deadline I/O scheduler

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/