> How about some test where relocations come into play?
> spec2000 is a bad example, it's just crunch code.
time ./configure might be a good test...
Agreed.
> Most systems spend their time running quick small executables over and
> over, and in such cases relocation overhead shows up very strongly.
Really? What workload besides configure does many small programs?
What do you do when you're developing code? make, edit, ldd, ls,
grep, etc.
Agreed for ls and cat, but I do not think it hurts for bash...
It does a lot of relocations in child processes, so I bet it will
matter. 'make' might be better off since it uses vfork but on the
other hand it does have quite sizable data structures.
-
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/