public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Cromie <jim.cromie@gmail.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.18-rc4-mm1  Run-time of Locking API testsuite
Date: Thu, 17 Aug 2006 14:06:56 -0600	[thread overview]
Message-ID: <44E4CC60.3080109@gmail.com> (raw)


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! |



I diffed the respective configs, saw nothing obvious in the following,
some of them look like theyd favor -mm1, if anything.

<trimming the obvious irrelevants>

[jimc@harpo lxbuild]$ diff linux-2.6.18-rc4-sk/.config 
linux-2.6.18-rc4-mm1-sk/.config
3,4c3,4
< # Linux kernel version: 2.6.18-rc4
< # Mon Aug  7 17:53:01 2006
---
 > # Linux kernel version: 2.6.18-rc4-mm1
 > # Sun Aug 13 09:19:25 2006

1451a1491
 > CONFIG_ENABLE_MUST_CHECK=y
1454a1495
 > CONFIG_DEBUG_SHIRQ=y
1482,1483c1525,1528
< CONFIG_FORCED_INLINING=y
< CONFIG_RCU_TORTURE_TEST=y
---
 > # CONFIG_PROFILE_LIKELY is not set
 > # CONFIG_FORCED_INLINING is not set
 > # CONFIG_DEBUG_SYNCHRO_TEST is not set
 > # CONFIG_RCU_TORTURE_TEST is not set
1486c1531
< CONFIG_DEBUG_STACK_USAGE=y
---
 > # CONFIG_DEBUG_STACK_USAGE is not set


will send full configs if useful.

             reply	other threads:[~2006-08-17 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 20:06 Jim Cromie [this message]
2006-08-17 21:40 ` 2.6.18-rc4-mm1 Run-time of Locking API testsuite Jesper Juhl
2006-08-17 21:54   ` Jim Cromie
2006-08-17 22:08 ` Nish Aravamudan
2006-08-17 22:54   ` Jim Cromie

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=44E4CC60.3080109@gmail.com \
    --to=jim.cromie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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