From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: ling.ma@intel.com, hpa@zytor.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] [x86] Optimize copy-page by reducing impact from HW prefetch
Date: Thu, 23 Jun 2011 09:04:48 +0200 [thread overview]
Message-ID: <20110623070448.GA25707@elte.hu> (raw)
In-Reply-To: <m2fwn13a3u.fsf@firstfloor.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> ling.ma@intel.com writes:
>
> > impact(DCU prefetcher), and simplify original code. The
> > performance is improved about 15% on core2, 36% on snb
> > respectively. (We use our micro-benchmark, and will do further
> > test according to your requirment)
>
> This doesn't make a lot of sense because neither Core-2 nor SNB use
> the code path you patched. They all use the rep ; movs path
Ling, mind double checking which one is the faster/better one on SNB,
in cold-cache and hot-cache situations, copy_page or copy_page_c?
Also, while looking at this file please fix the countless pieces of
style excrements it has before modifying it:
- non-Linux comment style (and needless two comments - it can
be in one comment block):
/* Don't use streaming store because it's better when the target
ends up in cache. */
/* Could vary the prefetch distance based on SMP/UP */
- (there's other non-standard comment blocks in this file as well)
- The copy_page/copy_page_c naming is needlessly obfuscated, it
should be copy_page, copy_page_norep or so - the _c postfix has no
obvious meaning.
- all #include's should be at the top
- please standardize it on the 'instrn %x, %y' pattern that we
generally use in arch/x86/, not 'instrn %x,%y' pattern.
and do this cleanup patch first and the speedup on top of it, and
keep the two in two separate patches so that the modification to the
assembly code can be reviewed more easily.
Thanks,
Ingo
next prev parent reply other threads:[~2011-06-23 7:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 22:51 [PATCH RFC] [x86] Optimize copy-page by reducing impact from HW prefetch ling.ma
2011-06-22 20:05 ` Andi Kleen
2011-06-23 1:01 ` Ma, Ling
2011-06-23 2:29 ` Andi Kleen
2011-06-23 7:04 ` Ingo Molnar [this message]
2011-06-24 2:01 ` Ma, Ling
2011-06-24 2:09 ` Ma, Ling
2011-06-28 15:23 ` Ma, Ling
2011-07-01 8:10 ` Ma, Ling
2011-07-01 10:26 ` Ma, Ling
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=20110623070448.GA25707@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=ling.ma@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox