Messages in this thread | | | Date | Sun, 6 Jul 2003 21:22:13 -0500 | From | Brandon Low <> | Subject | Re: anticipatory scheduler merged |
| |
On Sat, 07/05/03 at 13:33:34 -0700, Andrew Morton wrote: > - These changes have been well tested, but it is five months work and > over 100 patches. There's probably a bug or two. If you suspect that > something has gone wrong at the block layer (lots of tasks stuck in D > state) then please retest with `elevator=deadline'. > > Thanks.
I am seeing these D tasks when running 2.5.74-mm2 under a heavy seeking load (compiling application, untarring kernel, and filesharing simultaneously) on a slow (laptop 4200RPM) hdd. I find that after about 10 uptime when I start throwing on the seeking loads one or all of them go to D state and any new disk IO is either blocked or very slow.
I have tested with elevator=deadline and have been unable to reproduce.
Any further testing or debugging you need me to do I can probably do (but I'm not terribly knowledgable so I'll need step by step for said testing). Thanks!
Brandon Low - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |