All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ling Ma <ling.ma.program@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com,
	neleai@seznam.cz, linux-kernel@vger.kernel.org,
	Ling Ma <ling.ml@alibaba-inc.com>
Subject: Re: [PATCH RFC] x86:Improve memset with general 64bit instruction
Date: Sun, 13 Apr 2014 23:11:59 +0800	[thread overview]
Message-ID: <CAOGi=dMbRv6S+UGthYTCvW=C7hBRwpnZdM-BYYqT1fn=kF2SLg@mail.gmail.com> (raw)
In-Reply-To: <CAOGi=dPOEnNOLfnxTfvsVupRWQZtGs7-9LxDF8g2Kbun2v0hQA@mail.gmail.com>

Any further comments  ?

Thanks
Ling


2014-04-08 22:00 GMT+08:00, Ling Ma <ling.ma.program@gmail.com>:
> Andi,
>
> The below is compared result on older machine(cpu info is attached):
> That shows new code get better performance up to 1.6x.
>
> Bytes: ORG_TIME: NEW_TIME: ORG vs NEW:
> 7       0.87    0.76    1.14
> 16      0.99    0.68    1.45
> 18      1.07    0.77    1.38
> 21      1.09    0.78    1.39
> 25      1.11    0.77    1.44
> 30      1.12    0.73    1.53
> 36      1.15    0.75    1.53
> 38      1.12    0.75    1.49
> 62      1.18    0.77    1.53
> 75      1.25    0.79    1.58
> 85      1.28    0.80    1.60
> 120     1.33    0.82    1.62
> 193     1.45    0.88    1.64
> 245     1.48    0.96    1.54
> 256     1.45    0.90    1.61
> 356     1.61    1.02    1.57
> 601     1.78    1.22    1.45
> 958     2.04    1.47    1.38
> 1024    2.07    1.48    1.39
> 2048    2.80    2.21    1.26
>
> Thanks
> Ling
>
> 2014-04-08 0:42 GMT+08:00, Andi Kleen <andi@firstfloor.org>:
>> ling.ma.program@gmail.com writes:
>>
>>> From: Ling Ma <ling.ml@alibaba-inc.com>
>>>
>>> In this patch we manage to reduce miss branch prediction by
>>> avoiding using branch instructions and force destination to be aligned
>>> with general 64bit instruction.
>>> Below compared results shows we improve performance up to 1.8x
>>> (We modified test suit from Ondra, send after this patch)
>>
>> You didn't specify the CPU?
>>
>> I assume it's some Atom, as nothing else uses these open coded functions
>> anymore?
>>
>> -Andi
>>
>> --
>> ak@linux.intel.com -- Speaking for myself only
>>
>

  reply	other threads:[~2014-04-13 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 14:50 [PATCH RFC] x86:Improve memset with general 64bit instruction ling.ma.program
2014-04-07 14:52 ` Ling Ma
2014-04-07 16:42 ` Andi Kleen
2014-04-08 14:00   ` Ling Ma
2014-04-13 15:11     ` Ling Ma [this message]
2014-04-13 22:03       ` Andi Kleen
2014-04-14 13:31         ` Ling Ma
2014-04-15  5:01           ` Andi Kleen

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='CAOGi=dMbRv6S+UGthYTCvW=C7hBRwpnZdM-BYYqT1fn=kF2SLg@mail.gmail.com' \
    --to=ling.ma.program@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=ling.ml@alibaba-inc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=neleai@seznam.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.