From: Jim Cromie <jim.cromie@gmail.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18-rc4-mm1 Run-time of Locking API testsuite
Date: Thu, 17 Aug 2006 16:54:39 -0600 [thread overview]
Message-ID: <44E4F3AF.2030604@gmail.com> (raw)
In-Reply-To: <29495f1d0608171508k2f465419ue5b87ee2847ae3cd@mail.gmail.com>
Nish Aravamudan wrote:
> On 8/17/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! |
>
> This is more than just a dmesg difference, I assume? As in, you can
> actually tell the difference in time it takes?
>
yes - I can actually see individual cells (the 'ok's) in the table being
rendered separately.
This is across a serial line, at 115 kbaud, if that matters..
[ 22.762505] A-B-C-A-B-C deadlock: ok | ok | ok |
ok | ok | ok |
[ 26.589133] A-B-B-C-C-D-D-A deadlock: ok | ok | ok |
ok | ok | ok |
[ 31.854688] A-B-C-D-B-D-D-A deadlock: ok | ok | ok |
ok | ok | ok |
> Thanks,
> Nish
>
prev parent reply other threads:[~2006-08-17 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 20:06 2.6.18-rc4-mm1 Run-time of Locking API testsuite Jim Cromie
2006-08-17 21:40 ` Jesper Juhl
2006-08-17 21:54 ` Jim Cromie
2006-08-17 22:08 ` Nish Aravamudan
2006-08-17 22:54 ` Jim Cromie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44E4F3AF.2030604@gmail.com \
--to=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox