Bug#593720: marked as done (Fwd: Deadline as default scheduler?)
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 that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 593720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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 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). Cesare. Original Message Subject: Deadline as default scheduler? Date: Tue, 10 Aug 2010 00:04:44 +0200 From: Cesare Leonardi celeo...@gmail.com To: debian-kernel@lists.debian.org Hi all. I've noted some changes in the scheduler configuration of 2.6.35-trunk-686 and i wonder if they are erroneous or not, since their effect are rather evident and i've seen no discussion on d-k. I was filing a bug but i preferred to ask on the mailing list first. --- /boot/config-2.6.35-rc6-686 2010-07-26 13:09:56.0 +0200 +++ /boot/config-2.6.35-trunk-686 2010-08-06 18:13:52.0 +0200 @@ -221,11 +222,12 @@ # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y -CONFIG_IOSCHED_CFQ=y -# 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 scheduler? And why configuring cfq as module? In a desktop usage, with a pentium M 1,6 GHz and 1 GB ram, the system is clearly worse in responsiveness, a bit jerky in particular when i type on the keyboard: occasionaly i can see the effect of what i type with a delay of some tenth of second. Are there other distros not using cfq as default scheduler? Ciao. Cesare. Reply from Ben Subject: Re: Deadline as default scheduler? Date: Tue, 10 Aug 2010 01:58:14 +0100 From: Ben Hutchings b...@decadent.org.uk To: Cesare Leonardi celeo...@gmail.com, Maximilian Attems matt...@hep.itp.tuwien.ac.at CC: debian-kernel@lists.debian.org [...] 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 # If BLK_CGROUP is a module, CFQ has to be built as module. depends on (BLK_CGROUP=m m) || !BLK_CGROUP || BLK_CGROUP=y Max, we have to make BLK_CGROUP=y or disable it completely. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.35-1~experimental.3 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.35-1~experimental.3_all.deb linux-2.6_2.6.35-1~experimental.3.diff.gz to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.diff.gz linux-2.6_2.6.35-1~experimental.3.dsc to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.dsc linux-base_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-base_2.6.35-1~experimental.3_all.deb linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux
Bug#593720: Fwd: Deadline as default scheduler?
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 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 upload to experimental. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#593720: Fwd: Deadline as default scheduler?
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 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). Cesare. Original Message Subject: Deadline as default scheduler? Date: Tue, 10 Aug 2010 00:04:44 +0200 From: Cesare Leonardi celeo...@gmail.com To: debian-kernel@lists.debian.org Hi all. I've noted some changes in the scheduler configuration of 2.6.35-trunk-686 and i wonder if they are erroneous or not, since their effect are rather evident and i've seen no discussion on d-k. I was filing a bug but i preferred to ask on the mailing list first. --- /boot/config-2.6.35-rc6-686 2010-07-26 13:09:56.0 +0200 +++ /boot/config-2.6.35-trunk-686 2010-08-06 18:13:52.0 +0200 @@ -221,11 +222,12 @@ # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y -CONFIG_IOSCHED_CFQ=y -# 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 scheduler? And why configuring cfq as module? In a desktop usage, with a pentium M 1,6 GHz and 1 GB ram, the system is clearly worse in responsiveness, a bit jerky in particular when i type on the keyboard: occasionaly i can see the effect of what i type with a delay of some tenth of second. Are there other distros not using cfq as default scheduler? Ciao. Cesare. Reply from Ben Subject: Re: Deadline as default scheduler? Date: Tue, 10 Aug 2010 01:58:14 +0100 From: Ben Hutchings b...@decadent.org.uk To: Cesare Leonardi celeo...@gmail.com, Maximilian Attems matt...@hep.itp.tuwien.ac.at CC: debian-kernel@lists.debian.org [...] 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 # If BLK_CGROUP is a module, CFQ has to be built as module. depends on (BLK_CGROUP=m m) || !BLK_CGROUP || BLK_CGROUP=y Max, we have to make BLK_CGROUP=y or disable it completely. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c6e946b.8040...@gmail.com
Deadline as default scheduler?
Hi all. I've noted some changes in the scheduler configuration of 2.6.35-trunk-686 and i wonder if they are erroneous or not, since their effect are rather evident and i've seen no discussion on d-k. I was filing a bug but i preferred to ask on the mailing list first. --- /boot/config-2.6.35-rc6-686 2010-07-26 13:09:56.0 +0200 +++ /boot/config-2.6.35-trunk-686 2010-08-06 18:13:52.0 +0200 @@ -221,11 +222,12 @@ # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y -CONFIG_IOSCHED_CFQ=y -# 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 scheduler? And why configuring cfq as module? In a desktop usage, with a pentium M 1,6 GHz and 1 GB ram, the system is clearly worse in responsiveness, a bit jerky in particular when i type on the keyboard: occasionaly i can see the effect of what i type with a delay of some tenth of second. Are there other distros not using cfq as default scheduler? Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c607b7...@gmail.com
Re: Deadline as default scheduler?
On Tue, 2010-08-10 at 00:04 +0200, Cesare Leonardi wrote: Hi all. I've noted some changes in the scheduler configuration of 2.6.35-trunk-686 and i wonder if they are erroneous or not, since their effect are rather evident and i've seen no discussion on d-k. I was filing a bug but i preferred to ask on the mailing list first. --- /boot/config-2.6.35-rc6-686 2010-07-26 13:09:56.0 +0200 +++ /boot/config-2.6.35-trunk-686 2010-08-06 18:13:52.0 +0200 @@ -221,11 +222,12 @@ # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y -CONFIG_IOSCHED_CFQ=y -# 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 scheduler? And why configuring cfq as module? This is due to enabling BLK_CGROUP: config IOSCHED_CFQ tristate CFQ I/O scheduler # If BLK_CGROUP is a module, CFQ has to be built as module. depends on (BLK_CGROUP=m m) || !BLK_CGROUP || BLK_CGROUP=y Max, we have to make BLK_CGROUP=y or disable it completely. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
