Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752164AbbEBBAX (ORCPT ); Fri, 1 May 2015 21:00:23 -0400 Received: from mail-bn1bn0104.outbound.protection.outlook.com ([157.56.110.104]:53523 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750970AbbEBBAW (ORCPT ); Fri, 1 May 2015 21:00:22 -0400 Authentication-Results: c-s.fr; dkim=none (message not signed) header.d=none; Message-ID: <1430528414.16357.201.camel@freescale.com> Subject: Re: [v2,2/2] powerpc32: add support for csum_add() From: Scott Wood To: christophe leroy CC: Benjamin Herrenschmidt , Paul Mackerras , , Date: Fri, 1 May 2015 20:00:14 -0500 In-Reply-To: <553FD904.8000309@c-s.fr> References: <20150203113927.8604D1A5F14@localhost.localdomain> <20150325013023.GA7588@home.buserror.net> <553FD904.8000309@c-s.fr> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.10-0ubuntu1~14.10.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Originating-IP: [2601:2:5800:3f7:12bf:48ff:fe84:c9a0] X-ClientProxiedBy: BL2PR01CA0031.prod.exchangelabs.com (10.141.66.31) To BN3PR03MB1477.namprd03.prod.outlook.com (25.163.35.140) X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN3PR03MB1477; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601004)(5005006)(3002001);SRVR:BN3PR03MB1477;BCL:0;PCL:0;RULEID:;SRVR:BN3PR03MB1477; X-Forefront-PRVS: 05641FD966 X-Forefront-Antispam-Report: SFV:NSPM;SFS:(10019020)(6009001)(377424004)(24454002)(51704005)(479174004)(50466002)(23676002)(103116003)(92566002)(33646002)(86362001)(575784001)(77156002)(62966003)(42186005)(5001920100001)(47776003)(46102003)(122386002)(110136002)(50986999)(87976001)(36756003)(5820100001)(50226001)(5001960100002)(2950100001)(76176999);DIR:OUT;SFP:1102;SCL:1;SRVR:BN3PR03MB1477;H:[IPv6:2601:2:5800:3f7:12bf:48ff:fe84:c9a0];FPR:;SPF:None;MLV:sfv;LANG:en; X-OriginatorOrg: freescale.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 02 May 2015 01:00:20.3090 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR03MB1477 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2738 Lines: 84 On Tue, 2015-04-28 at 21:01 +0200, christophe leroy wrote: > > > Le 25/03/2015 02:30, Scott Wood a écrit : > > > On Tue, Feb 03, 2015 at 12:39:27PM +0100, LEROY Christophe wrote: > > > The C version of csum_add() as defined in include/net/checksum.h gives the > > > following assembly: > > > 0: 7c 04 1a 14 add r0,r4,r3 > > > 4: 7c 64 00 10 subfc r3,r4,r0 > > > 8: 7c 63 19 10 subfe r3,r3,r3 > > > c: 7c 63 00 50 subf r3,r3,r0 > > > > > > include/net/checksum.h also offers the possibility to define an arch specific > > > function. > > > This patch provides a ppc32 specific csum_add() inline function. > > What makes it 32-bit specific? > > > > > As far as I understand, the 64-bit will do a 64 bit addition, so we > will have to handle differently the carry, can't just be an addze like > in 32-bit. OK. Before I couldn't find where this was ifdeffed to 32-bit, but it's in patch 1/2. > The generated code is most likely different on ppc64. I have no ppc64 > compiler so I can't check what gcc generates for the following code: > > __wsum csum_add(__wsum csum, __wsum addend) > { > u32 res = (__force u32)csum; > res += (__force u32)addend; > return (__force __wsum)(res + (res < (__force u32)addend)); > } > > Can someone with a ppc64 compiler tell what we get ? With CONFIG_GENERIC_CPU: 0xc000000000001af8 <+0>: add r3,r3,r4 0xc000000000001afc <+4>: cmplw cr7,r3,r4 0xc000000000001b00 <+8>: mfcr r4 0xc000000000001b04 <+12>: rlwinm r4,r4,29,31,31 0xc000000000001b08 <+16>: add r3,r4,r3 0xc000000000001b0c <+20>: clrldi r3,r3,32 0xc000000000001b10 <+24>: blr The mfcr is particularly nasty, at least on our chips. With CONFIG_CPU_E6500: 0xc000000000001b30 <+0>: add r3,r3,r4 0xc000000000001b34 <+4>: cmplw cr7,r3,r4 0xc000000000001b38 <+8>: mfocrf r4,1 0xc000000000001b3c <+12>: rlwinm r4,r4,29,31,31 0xc000000000001b40 <+16>: add r3,r4,r3 0xc000000000001b44 <+20>: clrldi r3,r3,32 0xc000000000001b48 <+24>: blr Ideal (short of a 64-bit __wsum) would probably be something like (untested): add r3,r3,r4 srdi r5,r3,32 add r3,r3,r5 clrldi r3,r3,32 Or in C code (which would let the compiler schedule it better): static inline __wsum csum_add(__wsum csum, __wsum addend) { u64 res = (__force u64)csum; res += (__force u32)addend; return (__force __wsum)((u32)res + (res >> 32)); } -Scott -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/