I would guess you want preempt plus lock-break at least. rtsched may
give a small improvement if you run any real time (i.e. not SCHED_OTHER)
tasks (and the improvement should be in both real time and non-real time
preemption) but, in general, the schedule is not any where near the
problem the long held locks are so I really don't expect to see much
improvement here. If you have a lot of task on the system (not active,
just there) you may see the "recalculate" with the standard scheduler
which is much improved with rtsched (it does not include tasks not in
the run list in the recalculate).
As for high-res-timers, I just put out a 2.4.13 version which should
work on 2.4.17 (there are rejects in the patch, but all in non-i386
code). I have one report, however, of asm errors which seem to depend
on the compiler (or asm) version. I will look into this and put up a
2.4.17 version early next week. Testing wise, I don't think this will
be visible because you most likely are not using POSIX timers. There is
a change in the timer list structure, but that should be in the noise
also. In short, the high-res-timers project provides new capability,
not improved performance with existing capability.
>
> I ask because my MP3/Ogg-Vorbis hiccup during dbench isn't solved anyway.
> Running 2.4.17 + preempt + lock-break + 10_vm-21 (AA).
> Some wisdom?
Try the preempt-stats patch and collect data during the hiccup. It
should point the finger at the problem. Let us know what you find.
Robert has been very good at fixing things like this with his lock-break
stuff, but we/he need to know who the bad guy is.
>
> Thank you for all your work and
> Happy New Year
>
> -Dieter
> --
> Dieter Nützel
> Graduate Student, Computer Science
>
> University of Hamburg
> Department of Computer Science
> @home: Dieter.Nuetzel@hamburg.de
-- George george@mvista.com High-res-timers: http://sourceforge.net/projects/high-res-timers/ Real time sched: http://sourceforge.net/projects/rtsched/ - 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/