Deadline as default scheduler?

[Cesare Leonardi <celeonar@gmail.com>]

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.000000000 +0200
+++ /boot/config-2.6.35-trunk-686   2010-08-06 18:13:52.000000000 +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.