linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: christophe leroy <christophe.leroy@c-s.fr>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] powerpc32: put csum_tcpudp_magic inline
Date: Tue, 28 Apr 2015 21:08:57 +0200	[thread overview]
Message-ID: <553FDAC9.3050902@c-s.fr> (raw)
In-Reply-To: <1427249404.22867.86.camel@freescale.com>



Le 25/03/2015 03:10, Scott Wood a écrit :
> On Tue, 2015-02-03 at 12:39 +0100, Christophe Leroy wrote:
>> csum_tcpudp_magic() is only a few instructions, and does not modifies any other
>> register than the returned result. So it is not worth having it as a separate
>> function and suffer function branching and saving of volatile registers.
>> This patch makes it inline by use of the already existing csum_tcpudp_nofold()
>> function.
>>
>> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
>>
>> ---
>> v2: no change
>>
>>   arch/powerpc/include/asm/checksum.h | 15 +++++++++++++++
>>   arch/powerpc/lib/checksum_32.S      | 16 ----------------
>>   2 files changed, 15 insertions(+), 16 deletions(-)
> The 64-bit version is pretty similar to the 32-bit -- why only use
> csum_tcpudp_nofold() on 32-bit?
>
>
I did it only on 32-bit because I have no way to test it on 64-bits, but 
I can do it for 64 bits as well, no problem.

Christophe

---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
http://www.avast.com

      reply	other threads:[~2015-04-28 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 11:39 [PATCH v2 1/2] powerpc32: put csum_tcpudp_magic inline Christophe Leroy
2015-03-25  2:10 ` Scott Wood
2015-04-28 19:08   ` christophe leroy [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=553FDAC9.3050902@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).