> Due to recent "problems" (well the vm being just too damn good at keep
> disks busy these days), it's become even more apparent that our current
> io scheduler just cannot cope with some work loads. Repeated starvartion
> of reads is the most important one. The Andrew Morton Interactive
> Workload (AMIW) [1] rates the current kernel poorly, on my test machine
> it completes in 1-2 minutes depending on your luck. 2.5.38-BK does a lot
> better, but mainly because it's being extremely unfair. This deadline io
> scheduler finishes the AMIW in anywhere from ~0.5 seconds to ~3-4
> seconds, depending on the io load.
would it be possible to make deadlines per-process to introduce ionice?
ionice -n -5 mpg123 foo.mp3
ionice make
? Pavel
-- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.- 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/