From: Miao Xie <miaox@cn.fujitsu.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Ma, Ling" <ling.ma@intel.com>, Ingo Molnar <mingo@redhat.com>,
Andi Kleen <andi@firstfloor.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Zhao, Yakui" <yakui.zhao@intel.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 -tip] lib,x86_64: improve the performance of memcpy() for unaligned copy
Date: Mon, 18 Oct 2010 11:12:52 +0800 [thread overview]
Message-ID: <4CBBBB34.7060702@cn.fujitsu.com> (raw)
In-Reply-To: <4CB62543.7000605@zytor.com>
On Wed, 13 Oct 2010 14:31:47 -0700, H. Peter Anvin wrote:
> On 10/08/2010 02:02 AM, Miao Xie wrote:
>> On Fri, 8 Oct 2010 15:42:45 +0800, Ma, Ling wrote:
>>> Could you please give us full address for each comparison result,we will do some tests on my machine.
>>> For unaligned cases older cpus will crossing cache line and slow down caused by load and store, but for nhm, no necessary to care about it.
>>> By the way in kernel 64bit mode, our access mode should be around 8byte aligned.
>>
>> Would you need my benchmark tool? I think it is helpful for your test.
>>
>
> If you could post the benchmark tool that would be great.
The following is the URL of the benchmark tool that I have posted.
http://marc.info/?l=linux-kernel&m=128652854608425&q=p3
Thanks
Miao
prev parent reply other threads:[~2010-10-18 3:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 7:28 [PATCH V2 -tip] lib,x86_64: improve the performance of memcpy() for unaligned copy Miao Xie
2010-10-08 7:42 ` Ma, Ling
2010-10-08 9:02 ` Miao Xie
2010-10-13 21:31 ` H. Peter Anvin
2010-10-14 1:14 ` Ma, Ling
2010-10-14 19:43 ` Ma, Ling
2010-10-18 6:23 ` Miao Xie
2010-10-18 6:27 ` Ma, Ling
2010-10-18 6:34 ` Miao Xie
2010-10-18 6:43 ` Ma, Ling
2010-10-18 7:42 ` Miao Xie
2010-10-18 8:01 ` Ma, Ling
2010-10-19 2:53 ` Miao Xie
2010-10-19 4:06 ` Ma, Ling
2010-10-18 3:12 ` Miao Xie [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=4CBBBB34.7060702@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=ling.ma@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=yakui.zhao@intel.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