On January 5, 2002 21:50, vvikram _at_ av.stanford.edu wrote: > 2) further i seperately ran ./lat_proc fork; ./lat_proc exec; ./lat_proc > shell many times on the vanilla and patched kernels. their output is also > attached in one file [lat_proc.txt]. the patched kernel takes > MORE time than the vanilla one...... I'd blame this partially on the reverted fork() execution order bit of his patch. The child process really should be executed first, and performance is much improved in that case (COW and things). I don't think we should worry about breaking obviously incorrect (and already fragile) programs for 2.5.x. -Ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: [ingo patch] 2.4.17 benchmarksVikram <vvikram _at_ stanford.edu>
- [ingo patch] 2.4.17 benchmarksvvikram _at_ av.stanford.edu
- Prev by Date: Re: no highmem with 2GB RAM?
- Next by Date: Re: 2.5.2-pre performance degradation on an old 486
- Previous by thread: [ingo patch] 2.4.17 benchmarks
- Next by thread: Re: [ingo patch] 2.4.17 benchmarks
- Indexes:[Main][Thread]