Messages in this thread | | | Date | Thu, 10 Jan 2002 11:15:55 -0800 | From | Mike Kravetz <> | Subject | Re: [patch] O(1) scheduler, -D1, 2.5.2-pre9, 2.4.17 |
| |
On Thu, Jan 10, 2002 at 11:08:21AM -0800, Davide Libenzi wrote: > On Thu, 10 Jan 2002, Mike Kravetz wrote: > > > > > > I just kicked off another benchmark run to compare pre10, pre10 & G1 > > > patch, pre10 & Davide's patch. > > > > It wasn't a good night for benchmarking. I had a typo in the > > script to run chat reniced and as a result didn't collect any > > numbers for this. In addition, the kernel with Davide's patch > > failed to boot with 8 CPUs enabled. Can't see any '# CPU specific' > > mods in the patch. In any case, here is what I do have. > > Doh !! Do you have a panic dump Mike ?
It didn't panic, but hung during the boot process. After reading other mail, this may be caused by the out of order locking bug/deadlock that existed in this version of the O(1) scheduler. I may be able to try and verify later today. Right now the machine is being used for something else.
-- Mike - 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/
| |