>>>>> Badari Pulavarty (BP) writes:

 >> UP, after:
 >> [EMAIL PROTECTED] root]# time /work/tests/fwrite /test/fff 64 10000
 >> real    0m21.452s user    0m0.026s sys     0m6.105s
 >> [EMAIL PROTECTED] root]# time /work/tests/fwrite /test/fff 64 10000
 >> real    0m23.317s user    0m0.027s sys     0m4.206s
 >> [EMAIL PROTECTED] root]# time /work/tests/fwrite /test/fff 64 10000
 >> real    0m25.190s user    0m0.022s sys     0m4.026s
 >> [EMAIL PROTECTED] root]# time /work/tests/fwrite /test/fff 64 10000
 >> real    0m25.024s user    0m0.021s sys     0m4.103s
 >> UP, before:
 >> [EMAIL PROTECTED] root]# time /work/tests/fwrite /test/fff 64 10000
 >> real    0m19.138s user    0m0.021s sys     0m5.980s
 >> [EMAIL PROTECTED] root]# time /work/tests/fwrite /test/fff 64 10000
 >> real    0m23.123s user    0m0.026s sys     0m4.083s
 >> [EMAIL PROTECTED] root]# time /work/tests/fwrite /test/fff 64 10000
 >> real    0m25.152s user    0m0.017s sys     0m3.836s
 >> [EMAIL PROTECTED] root]# time /work/tests/fwrite /test/fff 64 10000
 >> real    0m25.217s user    0m0.026s sys     0m3.827s

 BP> Hmm.. On UP, the patch made sys.time little worse ?

grrrr. sorry, that's a typo. exchange 'after' and 'before' please.
btw, want to see how delayed allocation manages this?

thanks, Alex

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to