From: Borislav Petkov <bp@alien8.de>
To: George Spelvin <linux@horizon.com>
Cc: hpa@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] x86 fixes for 3.11-rc2
Date: Sat, 20 Jul 2013 18:55:55 +0200 [thread overview]
Message-ID: <20130720165555.GB13759@pd.tnic> (raw)
In-Reply-To: <20130720144758.13924.qmail@science.horizon.com>
On Sat, Jul 20, 2013 at 10:47:58AM -0400, George Spelvin wrote:
> Borislav Petkov <bp@alien8.de> wrote:
> > I don't think that matters because this is called only once on suspend.
> > Unless the cleaner assembly translates into a palpable speedup, which I
> > doubt.
>
> I was thinking about code *size*, actually; I agree that speed is
> too small to measure.
>
> Clean code (21 bytes):
> 4e: b9 80 00 00 c0 mov $0xc0000080,%ecx
> 53: 0f 32 rdmsr
> 55: 0f 30 wrmsr
> 57: 31 f6 xor %esi,%esi
> 59: 85 f6 test %esi,%esi
> 5b: 89 43 14 mov %eax,0x14(%ebx)
> 5e: 89 53 18 mov %edx,0x18(%ebx)
> 61: 75 04 jne 67 <acpi_suspend_lowlevel+0x67>
>
> Ugly code (50 bytes):
Right, that would matter maybe partially if the code was executed very
often. In that case, the probability of it fitting in one cacheline is
higher depending on alignment, and, you'd possibly save yourself loading
a second cacheline.
If it is 29 bytes bigger, than we have a higher probability for using a
second cacheline.
But again, I highly doubt even that would be noticeable. Especially on
modern uarches with very aggressive and smart branch prediction.
And since this is being called only once, you won't notice the
difference even with perf and specific instruction cache counters
enabled.
But what do I know - I'm always open to surprising workloads! :-)
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-07-20 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 12:25 [GIT PULL] x86 fixes for 3.11-rc2 George Spelvin
2013-07-20 13:25 ` Borislav Petkov
2013-07-20 14:47 ` George Spelvin
2013-07-20 16:55 ` Borislav Petkov [this message]
2013-07-21 20:17 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2013-07-18 22:41 H. Peter Anvin
2013-07-19 0:46 ` Linus Torvalds
2013-07-19 0:49 ` Myklebust, Trond
2013-07-19 0:50 ` H. Peter Anvin
2013-07-19 4:25 ` H. Peter Anvin
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=20130720165555.GB13759@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.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