From: Scott Wood <scottwood@freescale.com>
To: Laurentiu Tudor <Laurentiu.Tudor@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Patch not showing up in patchwork (was Re: [PATCH] powerpc/booke64: wrap tlb lock and search in htw miss with FTR_SMT)
Date: Fri, 30 May 2014 17:39:34 -0500 [thread overview]
Message-ID: <1401489574.6603.225.camel@snotra.buserror.net> (raw)
In-Reply-To: <1401461955-18007-1-git-send-email-Laurentiu.Tudor@freescale.com>
On Fri, 2014-05-30 at 17:59 +0300, Laurentiu Tudor wrote:
> Virtualized environments expose a e6500 dual-threaded core
> as two single-threaded e6500 cores. Take advantage of this
> and get rid of the tlb lock and the trap-causing tlbsx in
> the htw miss handler by guarding with CPU_FTR_SMT, as it's
> already being done in the bolted tlb1 miss handler.
>
> As seen in the results below, measurements done with lmbench
> random memory access latency test running under Freescale's
> Embedded Hypervisor, there is a ~34% improvement.
>
> Memory latencies in nanoseconds - smaller is better
> (WARNING - may not be correct, check graphs)
> ----------------------------------------------------
> Host Mhz L1 $ L2 $ Main mem Rand mem
> --------- --- ---- ---- -------- --------
> smt 1665 1.8020 13.2 83.0 1149.7
> nosmt 1665 1.8020 13.2 83.0 758.1
>
> Signed-off-by: Laurentiu Tudor <Laurentiu.Tudor@freescale.com>
> Cc: Scott Wood <scottwood@freescale.com>
> ---
> arch/powerpc/mm/tlb_low_64e.S | 4 ++++
> 1 file changed, 4 insertions(+)
Any idea why this patch isn't showing up on the mailing list? I see my
reply in the archives, but not the original patch.
-Scott
prev parent reply other threads:[~2014-05-30 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1401461955-18007-1-git-send-email-Laurentiu.Tudor@freescale.com>
2014-05-30 20:56 ` [PATCH] powerpc/booke64: wrap tlb lock and search in htw miss with FTR_SMT Scott Wood
2014-05-30 22:39 ` Scott Wood [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=1401489574.6603.225.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=Laurentiu.Tudor@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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).