All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: jeremy@goop.org,
	"asit.k.mallick@intel.com" <asit.k.mallick@intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	tglx@linutronix.de, Andi Kleen <ak@linux.intel.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>
Subject: Re: [RFC patch] cmpxchg_double: remove local variables to get better performance
Date: Sat, 03 Mar 2012 14:03:17 +0800	[thread overview]
Message-ID: <4F51B425.7090805@intel.com> (raw)
In-Reply-To: <4F50F594020000780007612D@nat28.tlf.novell.com>

On 03/02/2012 11:30 PM, Jan Beulich wrote:

>>>> On 02.03.12 at 16:12, Alex Shi <alex.shi@intel.com> wrote:
>> On 03/02/2012 05:11 PM, Jan Beulich wrote:
>>> In particular, requiring an L suffix here on literals should be avoided.
>>
>>
>> Even the each macro may save 0x40 bytes text, and bring more 10%
>> execution speed?
> 
> Again - if you see meaningful text size differences with optimization
> properly enabled, this may need investigation at the compiler end.


Yes, you are right.
I take back this patch.

> 
> Jan
> 



      reply	other threads:[~2012-03-03  6:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  8:31 [RFC patch] cmpxchg_double: remove local variables to get better performance Alex Shi
2012-03-02  8:54 ` Jan Beulich
2012-03-02  9:00   ` Alex Shi
2012-03-02  9:11     ` Jan Beulich
2012-03-02 15:12       ` Alex Shi
2012-03-02 15:30         ` Jan Beulich
2012-03-03  6:03           ` Alex Shi [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=4F51B425.7090805@intel.com \
    --to=alex.shi@intel.com \
    --cc=JBeulich@suse.com \
    --cc=ak@linux.intel.com \
    --cc=asit.k.mallick@intel.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 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.