I found a pathological case in 2.5 while running contest with process_load
recently after checking the results which showed a bad result for 2.5.43-mm1:
2.5.43-mm1 101.38 72% 42 31%
2.5.43-mm1 102.90 75% 34 28%
2.5.43-mm1 504.12 14% 603 85%
2.5.43-mm1 96.73 77% 34 26%
This was very strange so I looked into it further
The default for process_load is this command:
process_load --processes $nproc --recordsize 8192 --injections 2
where $nproc=4*num_cpus
When I changed recordsize to 16384, many of the 2.5 kernels started exhibiting
the same behaviour. While the machine was apparently still alive and would
respond to my request to abort, the kernel compile would all but stop while
process_load just continued without allowing anything to happen from kernel
compilation for up to 5 minutes at a time. This doesnt happen with any 2.4 kernels.
I'm not sure what to make of this. Suggestion?
Con
-
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 : Wed Oct 23 2002 - 22:00:31 EST