Messages in this thread | | | Date | Thu, 17 Aug 2006 23:40:21 +0200 | From | "Jesper Juhl" <> | Subject | Re: 2.6.18-rc4-mm1 Run-time of Locking API testsuite |
| |
On 17/08/06, Jim Cromie <jim.cromie@gmail.com> wrote: > > Note the non-trivial execution time difference: > > soekris:~/pinlab# egrep -e 'Locking|Good' dmesg-2.6.18-rc4-* > dmesg-2.6.18-rc4-mm1-sk:[ 16.044699] | Locking API testsuite: > dmesg-2.6.18-rc4-mm1-sk:[ 96.083576] Good, all 218 testcases passed! | > dmesg-2.6.18-rc4-sk:[ 18.563808] | Locking API testsuite: > dmesg-2.6.18-rc4-sk:[ 19.693692] Good, all 218 testcases passed! | > Interresting. On my box it takes at most a few seconds (don't have printk times enabled, so I can't give exact numbers). My best estimate is 2-3 seconds to run the self tests.
I wonder what's so different about our machines. Mine is a Athlon64 X2 4400+ w/ 2GB RAM.
relevant config options look identical to yours... Strange..
-- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - 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/
| |