mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: linguranus@gmail.com, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] [X86] performance improvement for memcpy_64.S by avoid memory miss predication.
Date: Mon, 19 Oct 2009 09:17:40 +0200	[thread overview]
Message-ID: <20091019071740.GA17407@elte.hu> (raw)
In-Reply-To: <1255928924-19140-1-git-send-email-linguranus@gmail.com>


* linguranus@gmail.com <linguranus@gmail.com> wrote:

> From: Ling <linguranus@gmail.com>
> 
> Hi All
> 
> CPU will use memory disambiguration predication to speculatively read 
> memory without waiting for previous write instructions and correctly 
> avoid conflict between them (RAW). However it seem only to care about 
> last 12 bits of address, not care about real address. For example if 
> rsi is 0xf004, rdi is 0xe008, when we do following operation there 
> will generate big performance latency.

Would be nice to trigger this kind of pattern via some testcase that 
uses read() or write() - or some other real workload.

Then you can use 'perf stat --repeat 10 ./my-test-prog' to measure it 
and post the results - the before-patch/after-patch instruction count, 
cycle count, etc.

You can get 'perf' via:

  cd tools/perf
  make -j install

(And please preserve the Cc: line for new postings - thanks.)

Thanks,

	Ingo

  reply	other threads:[~2009-10-19  7:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19  5:08 linguranus
2009-10-19  7:17 ` Ingo Molnar [this message]
     [not found]   ` <4b097b8f0910192240r254cb792gb5c3217c5bc71c8c@mail.gmail.com>
2009-10-20  6:33     ` Ingo Molnar

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=20091019071740.GA17407@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linguranus@gmail.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
Powered by JetHome