From: Nivedita Singhvi <niv@us.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: john stultz <johnstul@us.ibm.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: -O option causing test jitter?
Date: Tue, 22 Apr 2008 09:05:44 -0700 [thread overview]
Message-ID: <480E0CD8.2070400@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0804172120001.25316@gandalf.stny.rr.com>
Steven Rostedt wrote:
>
> On Thu, 17 Apr 2008, john stultz wrote:
>> Anyway, I wanted to hit the list with this so folks could look at it and
>> let me know if such severe jitter was expected from just compile
>> options?
>>
>
> I think this may simply be a simple case of cache misses.
>
> Attached is two files: sched_jitter-test.c and do_work.S. I found that by
> switching the positions of do_work1 and do_work2, which ever one is first
> performs better. do_work1 is me copying the output of objdump of -O1 of
> do_work, and do_work2 is copying the output from objdump of -O2.
So jitter going down might simply be a case of the
faster cases actually slowing down, right - and
making things uniformly slow?
Do we know if the whole kaboodle is getting faster?
thanks,
Nivedita
prev parent reply other threads:[~2008-04-22 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 23:59 -O option causing test jitter? john stultz
2008-04-18 2:17 ` Steven Rostedt
2008-04-22 16:05 ` Nivedita Singhvi [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=480E0CD8.2070400@us.ibm.com \
--to=niv@us.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).