All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Valdis.Kletnieks@vt.edu
Cc: ling.ma.program@gmail.com, mingo@redhat.com, tglx@linutronix.de,
	hpa@zytor.com, linux-kernel@vger.kernel.org,
	Ma Ling <ling.ml@alipay.com>
Subject: Re: [PATCH] [x86]: Compiler Option Os is better on latest x86
Date: Tue, 29 Jan 2013 09:12:03 +0100	[thread overview]
Message-ID: <20130129081203.GD594@gmail.com> (raw)
In-Reply-To: <26437.1359393357@turing-police.cc.vt.edu>


* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:

> On Fri, 25 Jan 2013 09:11:01 -0500, ling.ma.program@gmail.com said:
> 
> > Based on above reasons, we compiled linux kernel 3.6.9 with O2 and Os
> > respectively. The results show Os improve performance netperf 4.8%,
> > 2.7% for volano as below
> 
> Am I allowed to NAK this?  What the numbers given so far 
> *actually* show is 4.8% more instructions executed, *not* 4.8% 
> better performance.

cycles and elapsed time is down in both tests - the speedup 
seems statistically a wash in the first test and significant for 
the second workload.

the instruction count might be an artifact of byte wise versus 
word wise REP; MOV.

> I'm having a *very* hard time convincing myself that what 
> we're seeing isn't simply the expected behavior of loops *not* 
> being unrolled and similar non-optimizations done by -Os, so 
> more instructions get executed to do the same amount of work.
> 
> Rather than "run for 10 seconds and count instructions", can 
> we "run for 50,000 syscalls and count clock time" or similar 
> that shows an *actual* improvement?

Look at the numbers, it counts a whole lot of other things as 
well beyond instructions - elapsed time being the most important 
one.

But more numbers never hurt.

Thanks,

	Ingo

      reply	other threads:[~2013-01-29  8:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 14:11 [PATCH] [x86]: Compiler Option Os is better on latest x86 ling.ma.program
2013-01-26 12:25 ` [tip:x86/asm] x86/defconfig: Turn on CONFIG_CC_OPTIMIZE_FOR_SIZE= y in the 64-bit defconfig tip-bot for Ma Ling
2013-01-26 12:52   ` Borislav Petkov
2013-01-26 15:18     ` H. Peter Anvin
2013-01-26 15:42       ` Borislav Petkov
2013-01-26 19:43       ` Linus Torvalds
2013-01-26 21:02         ` Steven Rostedt
2013-01-26 21:04           ` H. Peter Anvin
2013-01-27 12:49           ` Ingo Molnar
2013-01-26 21:08         ` H. Peter Anvin
2013-01-28 17:15 ` [PATCH] [x86]: Compiler Option Os is better on latest x86 Valdis.Kletnieks
2013-01-29  8:12   ` Ingo Molnar [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=20130129081203.GD594@gmail.com \
    --to=mingo@kernel.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=hpa@zytor.com \
    --cc=ling.ma.program@gmail.com \
    --cc=ling.ml@alipay.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.