At 10:30 PM 14/07/2002 -0700, Andrew Morton wrote:
>Funny thing about your results is the presence of sched_yield(),
>especially in the copy-from-pagecache-only load. That test should
>peg the CPU at 100% and definitely shouldn't be spending time in
>default_idle. So who is calling sched_yield()? I think it has to be
>your test app?
>
>Be aware that the sched_yield() behaviour in 2.5 has changed a lot
>wrt 2.4. It has made StarOffice 5.2 completely unusable on a non-idle
>system, for a start. (This is a SO problem and not a kernel problem,
>but it's a lesson).
my test app uses pthreads (one thread per disk-worker) and
pthread_cond_wait in the master task to wait for all workers to finish.
i'll switch the app to use clone() and sys_futex instead.
i guess in that case, its debatable whether its a kernel problem or not --
pthreads is out there, and if its default behavior is bad, any threaded app
which uses it will also be bad.
cheers,
lincoln.
-
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/
This archive was generated by hypermail 2b29 : Mon Jul 15 2002 - 22:00:29 EST