CHED_CFQ=m
+CONFIG_CFQ_GROUP_IOSCHED=y
+CONFIG_DEFAULT_DEADLINE=y
+# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
-CONFIG_DEFAULT_IOSCHED="cfq"
+CONFIG_DEFAULT_IOSCHED="deadline"
Why setting deadline as default scheduler? And why configuring cfq as
module?
In a d
-CONFIG_DEFAULT_IOSCHED="cfq"
> +CONFIG_DEFAULT_IOSCHED="deadline"
>
> Why setting deadline as default scheduler? And why configuring cfq as
> module?
This is due to enabling BLK_CGROUP:
config IOSCHED_CFQ
tristate "CFQ I/O scheduler"
experimental.2 the CFQ scheduler is yet configured as module and
deadline is the default scheduler (with evident negative impact on
responsiveness, at least on my not so young Pentium M 1,6 GHz).
Cesare.
Original Message
Subject: Deadline as default scheduler?
Date: Tue, 10 Aug
On Fri, 2010-08-20 at 16:42 +0200, Cesare Leonardi wrote:
> Package: linux-2.6
> Version: 2.6.35-1~experimental.2
> Severity: normal
>
> This bug report is just a reminder that comes from a message i sent on
> d-k mailing list: appended inline my initial message and the reply from
> Ben Hutching
Your message dated Mon, 06 Sep 2010 16:26:38 +
with message-id
and subject line Bug#593720: fixed in linux-2.6 2.6.35-1~experimental.3
has caused the Debian Bug report #593720,
regarding Fwd: Deadline as default scheduler?
to be marked as done.
This means that you claim that the problem has
5 matches
Mail list logo