Bad berformance with io scheduler cfg (which might be standard in generic kernel)

Bug #81640 reported by Markus Kienast
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.17-10-generic

When using the i686 kernel in Dapper or when I use the generic kernel in Edgy my system performs very badly! It is as if the apps would only be allowed to use a short frame of kernel time every 4 seconds or so.

That's why I switched to the i386 kernel, which works fine.

Worked fine, I mean, until I read about tweaking kernel performance by turning on the cfq io scheduler in the kernel at boot time by appending elevator=cfq.

Here I was again, experiencing the problems I had with i686 and generic kernels on the i386 kernel now.

This is, why I suspect that in generic and i686 kernels the same kernel option might be activated by default and for that reason these kernels produce the same problems. I read that redhat is using this in the default kernel, so Ubuntu might as well. So let me tell you, this scheduler is buggy! DON'T USE IT! It is at least buggy on my hardware and a friend of mine seems to experience similar problems. I will attach an lshw.

Revision history for this message
Markus Kienast (elias1884) wrote :
Revision history for this message
Markus Kienast (elias1884) wrote :

This might also be related to the following two bugs #72616 and #68548.

Revision history for this message
Markus Kienast (elias1884) wrote :

Just to get the links in here:
Bug #72616 and bug #68548

Revision history for this message
Markus Kienast (elias1884) wrote :

Please close/reject this bug. The reason must be something else. Tried all available schedulers (deadline etc.) with the same result. Did file a more specific bug here: bug #118765

Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

Closing at the reporters request.

Changed in linux-source-2.6.17:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.