Bug#593720: marked as done (Fwd: Deadline as default scheduler?)

2010-09-06 Thread Debian Bug Tracking System
Your message dated Mon, 06 Sep 2010 16:26:38 + with message-id e1osewk-0003jg...@franck.debian.org 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

Bug#593720: Fwd: Deadline as default scheduler?

2010-08-26 Thread Ben Hutchings
. The original message was about 2.6.35-1~experimental.1, but in 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). This will be fixed in the next

Bug#593720: Fwd: Deadline as default scheduler?

2010-08-20 Thread Cesare Leonardi
, but in 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

Deadline as default scheduler?

2010-08-09 Thread Cesare Leonardi
+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 desktop usage, with a pentium M 1,6

Re: Deadline as default scheduler?

2010-08-09 Thread Ben Hutchings
-# CONFIG_DEFAULT_DEADLINE is not set -CONFIG_DEFAULT_CFQ=y +CONFIG_IOSCHED_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