From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6168DA00C3; Thu, 23 Jun 2022 09:55:22 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E3C6F42824; Thu, 23 Jun 2022 09:55:06 +0200 (CEST) Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2056.outbound.protection.outlook.com [40.107.20.56]) by mails.dpdk.org (Postfix) with ESMTP id D7AB04069C; Thu, 23 Jun 2022 07:22:00 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=NblvIeVICkabewHrySSxOfJBsW/A1pNCJcchX8iG2w8ZAbVamVghReHIVukXLxUK+d+HdRCGBwpnSkY74fi4J1v0Fj0cqSGSj0gmFwqNR88wd1jUgJSXH7W42QCq/EcCeX8Wc6U+H/W+z7GkVFuKTKKozee7BLcg1IkkomKUGwKHrk+KyxPSfUPT0cLyjC8eMvLDDAg40EbZohCaAO8Kz0I4PzGVOBHfUIMkbcBykWKO0wXL6wL8jwkRG7W9/mi3EC5K0DkdUzH8HN+49erzZ6iGE5X9UQJTeKXaSSu9UxLF5hHh3ZHy5ByvyJBiOqxbpKDoVXtZcAnbsX9jR1kQRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=oPEBJvnw2AFCo9N+Keci6sfOwaOnNGj15Xh7xJ4FgU8=; b=hx3DhDEmgLYw4wzrwIhN37LG2Tiyl8FP5zLTZkTifRkxy6r4xGeEPMFaSBpsOURme3l54RBhzPdTDGrog023olWOWi4Pq8LzQYHG4h+iHBZEDSEnNVKr3vubwp5kaDy4Dl8Ke3+Ahyho8kJWyBkkJxfIvSFwLavIEsaq5hDaOE2cnMDTzPB1YBZnVETBcINETQqC8V3HITx0TS/E8+9Oj0atQiNrZ5fIjuTRTbe7NDspnWt/fJQ5sgnb9EE4jmFkuREl/3Q3cT0xQBNxmQ1OiFu6NtCCAD2UmkG6RIb0X1xh9d3UkmsRiVPeGJ0biQbgrlLYSGCcvpDnBNTPF79mNg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oPEBJvnw2AFCo9N+Keci6sfOwaOnNGj15Xh7xJ4FgU8=; b=qUPw6i1fvNXBp8/Zcyy0t1ap8DOrcoHyWWMa4vlGBNbM0ZN6aIN8PnWtDojjp3KI2uXG7jTELVgbmY8mscSygC5eZcG9jKuj3/qPM8WJbXCOy3h0abJs6SZD0ie4r5wB0iWTaDJPAqYz53Zo4bz4TiYjl1sD6wcpLYaFO7wZSe8= Received: from AM8PR07MB7666.eurprd07.prod.outlook.com (2603:10a6:20b:240::23) by AM0PR07MB5953.eurprd07.prod.outlook.com (2603:10a6:208:108::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5373.16; Thu, 23 Jun 2022 05:21:59 +0000 Received: from AM8PR07MB7666.eurprd07.prod.outlook.com ([fe80::188:e139:774e:cea1]) by AM8PR07MB7666.eurprd07.prod.outlook.com ([fe80::188:e139:774e:cea1%7]) with mapi id 15.20.5373.015; Thu, 23 Jun 2022 05:21:53 +0000 From: Emil Berg To: =?iso-8859-1?Q?Morten_Br=F8rup?= , Bruce Richardson CC: Stephen Hemminger , "stable@dpdk.org" , "bugzilla@dpdk.org" , "hofors@lysator.liu.se" , "olivier.matz@6wind.com" , "dev@dpdk.org" Subject: RE: [PATCH] net: fix checksum with unaligned buffer Thread-Topic: [PATCH] net: fix checksum with unaligned buffer Thread-Index: AQHYgiaa5HfwvbWOiEyQ5g/wygBtSq1TTuaAgATMtJCAAAQg8IABVuVggAAFVwCAABAOAIAAFBGAgAFa5uCAADK3AIAAI7mAgAAOwgCAABrZ4IABAW+g Date: Thu, 23 Jun 2022 05:21:53 +0000 Message-ID: References: <98CBD80474FA8B44BF855DF32C47DC35D87139@smartserver.smartshare.dk> <20220617084505.62071-1-mb@smartsharesystems.com> <98CBD80474FA8B44BF855DF32C47DC35D8713A@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35D87141@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35D87145@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35D87148@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35D87152@smartserver.smartshare.dk> <98CBD80474FA8B44BF855DF32C47DC35D87154@smartserver.smartshare.dk> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D87154@smartserver.smartshare.dk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com; x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 9bb55e0b-f473-47c7-e869-08da54d848b9 x-ms-traffictypediagnostic: AM0PR07MB5953:EE_ x-microsoft-antispam-prvs: x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: 0ud978/CXwU89TWBpFD+6a38BqnYNc3RycboBDjlQ+sefUGuqJDIX0RCxmhDgZIKqmKBe1M4tvyMG15DHxBhTpuumyEvR6pbQL14SPjmxZUQGxi9zoEKXG4NKq8QxrJbx+aSqGTXeHwLgFUmtJXLghtbcl/Oh0x2a7bUqf46pKlGf6nDtKHKNVkNWWkGeYnZCb0bTVGBMWwIJNDS0aSnglCiscehOhRrwwQy+xUaz3VZeKRxlGGOdqkZQpbbay1zK0kj11QPvm+jhHAywv2HQxgvUbzTFx8cJ7LzVaJE4fceOOzBi3mdz8ydUimv3A9nIIthFmLbcuto/x+vLirHHovV9HPeeOpA1hdH9N9CP0U6GpyeilvBAt0lLFW+fRee643Zp6Q2GtBqLxPsSF75SItFdhiOKf5hRPtxrTUIbklon1kL2cWvJ4bcn0N2tAe/+jnXC2HCw6fOA/LiWeYkynOFbwCsSkUOz7oo5ZBbKAarhYz33gaIhCQwvTeiH2lNnbZl1uc9pul/7xQSdL8AFKDgoxPPxIBfGuG3ORXWFcbEYDu/O2FxurBH5dHnt+qE0JyW+qq0hGejaeupeIz3FaULvmy2HzOHCBhIk/lHFPrsLGmRG9MwDGGyzaqfDpCZWOK1jDKAXrMhSp148NNfBWRzWtFQvw8i2FTU8/WrSUg2JyvCKfRJ0+RdL4BwG0wJNuZMW8DdJ0BdQB645P7RsRTx1/Ay8lPAMn+wR9vjm1cURvtt9gtrvX4yRG9chqeMr6Uct6VLUYk9p87jVbtylC9ILpYfZu2wtYy8seCoS6PLK9t6Tg1Oze3eTAJPNfWO1HdFACZUWqrgUT5kM4BvGA== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM8PR07MB7666.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230016)(4636009)(136003)(396003)(376002)(366004)(346002)(39860400002)(30864003)(2906002)(9686003)(44832011)(55016003)(38100700002)(8936002)(41300700001)(478600001)(52536014)(122000001)(83380400001)(7696005)(6506007)(316002)(71200400001)(82960400001)(966005)(66946007)(54906003)(53546011)(5660300002)(186003)(33656002)(26005)(66574015)(66476007)(110136005)(86362001)(64756008)(8676002)(66556008)(38070700005)(76116006)(4326008)(66446008); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: k8S//7wIVVq8vtQ4QZ5XKuyAvqV3q/M5rvdnoMtxIYFOBjXugzXMob2yptcB5DJy/njelXCd4vA5LYMp5pioTqi7V8KYWRLaBjQf5xgPIPDbMqxt62iUUCSJt3fMoHGtOlH666ejpgqoaNgcg0nPAWZaqeuIvESXcQTgP4vUz1mKYfJWrKyOpO/ySNEA3Nag8zgqdq0Soq6dJG3EuJJKI8G8BrHrVxT2JZ8vAHSd6Kn1UJF3ZvE3duhqkkPIrJZB2fQ7quSutVfWwB1slH2sWXbG4hEzF/QLZA2f1IfCIUk//pmiDaWulbooIixhGwm6x92QLtgJJ9pbySohdTZ3+kq3noG0ijisypDt44ctjITsQ0XKEcI75wrLuNEO2DKOIcEU5N5eBNubEEgnH6Sdyo/TUFH3ivgacF8RVgDklbwQWI7WtPgznUX6cnWXIZPG2pZldDP+k36fHSSWSQW9JVWCG93i8cUTvEh7eqNitzXyRAUrS5gpJG7KGTCvwbAxNrjOKmRO6ruDcncpj8/24pIsBx8dI13L1rffIiV3ZDksbMyASuQbaM6KplvWkwJ+w5xBWmiPAKIkfQhL55dxxXUohXNKhsE2tDOMh0ndQmAq7UbBbHcmqMRVN1TMebDGcfGXo58lQaYHhWBKpWwh/+dQ9LrEoTOn0rhVDh1DDlOL/sZa5Z3EVWCK6EtyIM8mujVgyA7B8SJAl2shHznOtH9a3z6RmVGjTbdvv9vBye7lP+I7bFG5khNhGkwF5h5o Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: ericsson.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: AM8PR07MB7666.eurprd07.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 9bb55e0b-f473-47c7-e869-08da54d848b9 X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jun 2022 05:21:53.5846 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: eXU1/4d3cmUm5jDGPNqUfbIIiLlmijGqVgCnxgcHzsTJjDmvu8gmjjkWSEuF4X5CEa9IHujUaqecDOUjLifjdg== X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB5953 X-Mailman-Approved-At: Thu, 23 Jun 2022 09:55:03 +0200 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org > -----Original Message----- > From: Morten Br=F8rup > Sent: den 22 juni 2022 16:02 > To: Emil Berg ; Bruce Richardson > > Cc: Stephen Hemminger ; > stable@dpdk.org; bugzilla@dpdk.org; hofors@lysator.liu.se; > olivier.matz@6wind.com; dev@dpdk.org > Subject: RE: [PATCH] net: fix checksum with unaligned buffer >=20 > > From: Emil Berg [mailto:emil.berg@ericsson.com] > > Sent: Wednesday, 22 June 2022 14.25 > > > > > From: Morten Br=F8rup > > > Sent: den 22 juni 2022 13:26 > > > > > > > From: Bruce Richardson [mailto:bruce.richardson@intel.com] > > > > Sent: Wednesday, 22 June 2022 11.18 > > > > > > > > On Wed, Jun 22, 2022 at 06:26:07AM +0000, Emil Berg wrote: > > > > > > > > > > > From: Morten Br=F8rup > > > > > > Sent: den 21 juni 2022 11:35 > > > > > > > > > > > > > From: Bruce Richardson [mailto:bruce.richardson@intel.com] > > > > > > > Sent: Tuesday, 21 June 2022 10.23 > > > > > > > > > > > > > > On Tue, Jun 21, 2022 at 10:05:15AM +0200, Morten Br=F8rup > > wrote: > > > > > > > > +TO: @Bruce and @Stephen: You signed off on the 16 bit > > > > alignment > > > > > > > requirement. We need background info on this. > > > > > > > > > > > > > > > > > From: Emil Berg [mailto:emil.berg@ericsson.com] > > > > > > > > > Sent: Tuesday, 21 June 2022 09.17 > > > > > > > > > > > > > > > > > > > From: Morten Br=F8rup > > > > > > > > > > Sent: den 20 juni 2022 12:58 > > > > > > > > > > > > > > > > > > > > > From: Emil Berg [mailto:emil.berg@ericsson.com] > > > > > > > > > > > Sent: Monday, 20 June 2022 12.38 > > > > > > > > > > > > > > > > > > > > > > > From: Morten Br=F8rup > > > > > > > > > > > > Sent: den 17 juni 2022 11:07 > > > > > > > > > > > > > > > > > > > > > > > > > From: Morten Br=F8rup > > > > > > > > > > > > > [mailto:mb@smartsharesystems.com] > > > > > > > > > > > > > Sent: Friday, 17 June 2022 10.45 > > > > > > > > > > > > > > > > > > > > > > > > > > With this patch, the checksum can be calculated > > on > > > > > > > > > > > > > an > > > > > > > unligned > > > > > > > > > > > > > part > > > > > > > > > > > of > > > > > > > > > > > > > a packet buffer. > > > > > > > > > > > > > I.e. the buf parameter is no longer required to > > be > > > > > > > > > > > > > 16 > > > > bit > > > > > > > > > aligned. > > > > > > > > > > > > > > > > > > > > > > > > > > The DPDK invariant that packet buffers must be > > > > > > > > > > > > > 16 bit > > > > > > > aligned > > > > > > > > > > > remains > > > > > > > > > > > > > unchanged. > > > > > > > > > > > > > This invariant also defines how to calculate the > > 16 > > > > bit > > > > > > > > > checksum > > > > > > > > > > > > > on > > > > > > > > > > > an > > > > > > > > > > > > > unaligned part of a packet buffer. > > > > > > > > > > > > > > > > > > > > > > > > > > Bugzilla ID: 1035 > > > > > > > > > > > > > Cc: stable@dpdk.org > > > > > > > > > > > > > > > > > > > > > > > > > > Signed-off-by: Morten Br=F8rup > > > > > > > > > > > > > > > > > --- > > > > > > > > > > > > > lib/net/rte_ip.h | 17 +++++++++++++++-- > > > > > > > > > > > > > 1 file changed, 15 insertions(+), 2 > > > > > > > > > > > > > deletions(-) > > > > > > > > > > > > > > > > > > > > > > > > > > diff --git a/lib/net/rte_ip.h b/lib/net/rte_ip.h > > > > index > > > > > > > > > > > > > b502481670..8e301d9c26 100644 > > > > > > > > > > > > > --- a/lib/net/rte_ip.h > > > > > > > > > > > > > +++ b/lib/net/rte_ip.h > > > > > > > > > > > > > @@ -162,9 +162,22 @@ __rte_raw_cksum(const void > > > > > > > > > > > > > *buf, > > > > > > > size_t > > > > > > > > > len, > > > > > > > > > > > > > uint32_t sum) { > > > > > > > > > > > > > /* extend strict-aliasing rules */ > > > > > > > > > > > > > typedef uint16_t > > > __attribute__((__may_alias__)) > > > > > > > u16_p; > > > > > > > > > > > > > - const u16_p *u16_buf =3D (const u16_p *)buf; > > > > > > > > > > > > > - const u16_p *end =3D u16_buf + len / > > > > sizeof(*u16_buf); > > > > > > > > > > > > > + const u16_p *u16_buf; > > > > > > > > > > > > > + const u16_p *end; > > > > > > > > > > > > > + > > > > > > > > > > > > > + /* if buffer is unaligned, keeping it byte > > > > order > > > > > > > > > independent */ > > > > > > > > > > > > > + if (unlikely((uintptr_t)buf & 1)) { > > > > > > > > > > > > > + uint16_t first =3D 0; > > > > > > > > > > > > > + if (unlikely(len =3D=3D 0)) > > > > > > > > > > > > > + return 0; > > > > > > > > > > > > > + ((unsigned char *)&first)[1] =3D > > > *(const > > > > unsigned > > > > > > > > > > > > char *)buf; > > > > > > > > > > > > > + sum +=3D first; > > > > > > > > > > > > > + buf =3D (const void *)((uintptr_t)buf > > > + 1); > > > > > > > > > > > > > + len--; > > > > > > > > > > > > > + } > > > > > > > > > > > > > > > > > > > > > > > > > > + u16_buf =3D (const u16_p *)buf; > > > > > > > > > > > > > + end =3D u16_buf + len / sizeof(*u16_buf); > > > > > > > > > > > > > for (; u16_buf !=3D end; ++u16_buf) > > > > > > > > > > > > > sum +=3D *u16_buf; > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > 2.17.1 > > > > > > > > > > > > > > > > > > > > > > > > @Emil, can you please test this patch with an > > > > > > > > > > > > unaligned > > > > > > > buffer on > > > > > > > > > > > your > > > > > > > > > > > > application to confirm that it produces the > > expected > > > > result. > > > > > > > > > > > > > > > > > > > > > > Hi! > > > > > > > > > > > > > > > > > > > > > > I tested the patch. It doesn't seem to produce the > > same > > > > > > > results. I > > > > > > > > > > > think the problem is that it always starts summing > > from > > > > an > > > > > > > > > > > even address, the sum should always start from the > > first > > > > byte > > > > > > > according > > > > > > > > > to > > > > > > > > > > > the checksum specification. Can I instead propose > > > > something > > > > > > > Mattias > > > > > > > > > > > R=F6nnblom sent me? > > > > > > > > > > > > > > > > > > > > I assume that it produces the same result when the > > "buf" > > > > > > > parameter is > > > > > > > > > > aligned? > > > > > > > > > > > > > > > > > > > > And when the "buf" parameter is unaligned, I don't > > expect > > > > it to > > > > > > > > > produce the > > > > > > > > > > same results as the simple algorithm! > > > > > > > > > > > > > > > > > > > > This was the whole point of the patch: I expect the > > > > > > > > > > overall > > > > > > > packet > > > > > > > > > buffer to > > > > > > > > > > be 16 bit aligned, and the checksum to be a partial > > > > checksum of > > > > > > > such > > > > > > > > > a 16 bit > > > > > > > > > > aligned packet buffer. When calling this function, I > > > > > > > > > > assume > > > > that > > > > > > > the > > > > > > > > > "buf" and > > > > > > > > > > "len" parameters point to a part of such a packet > > buffer. > > > > If > > > > > > > these > > > > > > > > > > expectations are correct, the simple algorithm will > > > > > > > > > > produce > > > > > > > incorrect > > > > > > > > > results > > > > > > > > > > when "buf" is unaligned. > > > > > > > > > > > > > > > > > > > > I was asking you to test if the checksum on the packet > > is > > > > > > > > > > correct > > > > > > > > > when your > > > > > > > > > > application modifies an unaligned part of the packet > > and > > > > uses > > > > > > > this > > > > > > > > > function to > > > > > > > > > > update the checksum. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Now I understand your use case. Your use case seems to > > > > > > > > > be > > > > about > > > > > > > partial > > > > > > > > > checksums, of which some partial checksums may start on > > > > unaligned > > > > > > > > > addresses in an otherwise aligned packet. > > > > > > > > > > > > > > > > > > Our use case is about calculating the full checksum on a > > > > nested > > > > > > > packet. > > > > > > > > > That nested packet may start on unaligned addresses. > > > > > > > > > > > > > > > > > > The difference is basically if we want to sum over > > aligned > > > > > > > addresses or > > > > > > > > > not, handling the heading and trailing bytes > > appropriately. > > > > > > > > > > > > > > > > > > Your method does not work in our case since we want to > > treat > > > > the > > > > > > > first > > > > > > > > > two bytes as the first word in our case. But I do > > understand > > > > that > > > > > > > both > > > > > > > > > methods are useful. > > > > > > > > > > > > > > > > Yes, that certainly are two different use cases, requiring > > two > > > > > > > different ways of calculating the 16 bit checksum. > > > > > > > > > > > > > > > > > > > > > > > > > > Note that your method breaks the API. Previously > > (assuming > > > > > > > > > no > > > > > > > crashing > > > > > > > > > due to low optimization levels, more accepting hardware, > > or > > > > > > > > > a > > > > > > > different > > > > > > > > > compiler (version)) the current method would calculate > > the > > > > > > > > > checksum assuming the first two bytes is the first word. > > > > > > > > > > > > > > > > > > > > > > > > > Depending on the point of view, my patch either fixes a > > > > > > > > bug > > > > (where > > > > > > > the checksum was calculated incorrectly when the buf pointer > > was > > > > > > > unaligned) or breaks the API (by calculating the differently > > > > > > > when > > > > the > > > > > > > buffer is unaligned). > > > > > > > > > > > > > > > > I cannot say with certainty which one is correct, but > > perhaps > > > > some > > > > > > > > of > > > > > > > the people with a deeper DPDK track record can... > > > > > > > > > > > > > > > > @Bruce and @Stephen, in 2019 you signed off on a patch [1] > > > > > > > introducing a 16 bit alignment requirement to the Ethernet > > > > address > > > > > > > structure. > > > > > > > > > > > > > > > > It is my understanding that DPDK has an invariant > > > > > > > > requiring > > > > packets > > > > > > > to be 16 bit aligned, which that patch supports. Is this > > > > invariant > > > > > > > documented anywhere, or am I completely wrong? If I'm wrong, > > > > > > > then > > > > the > > > > > > > alignment requirement introduced in that patch needs to be > > > > removed, as > > > > > > > well as any similar alignment requirements elsewhere in DPDK. > > > > > > > > > > > > > > I don't believe it is explicitly documented as a global > > > > invariant, but > > > > > > > I think it should be unless there is a definite case where > > > > > > > we > > > > need to > > > > > > > allow packets to be completely unaligned. Across all packet > > > > headers we > > > > > > > looked at, there was no tunneling protocol where the > > resulting > > > > packet > > > > > > > was left unaligned. > > > > > > > > > > > > > > That said, if there are real use cases where we need to > > > > > > > allow > > > > packets > > > > > > > to start at an unaligned address, then I agree with you that > > we > > > > need > > > > > > > to roll back the patch and work to ensure everything works > > with > > > > > > > unaligned addresses. > > > > > > > > > > > > > > /Bruce > > > > > > > > > > > > > > > > > > > @Emil, can you please describe or refer to which tunneling > > > > > > protocol > > > > you are > > > > > > using, where the nested packet can be unaligned? > > > > > > > > > > > > I am asking to determine if your use case is exotic (maybe > > > > > > some > > > > Ericsson > > > > > > proprietary protocol), or more generic (rooted in some > > > > > > standard > > > > protocol). > > > > > > This information affects the DPDK community's opinion about > > > > > > how > > it > > > > should > > > > > > be supported by DPDK. > > > > > > > > > > > > If possible, please provide more details about the tunneling > > > > protocol and > > > > > > nested packets... E.g. do the nested packets also contain > > > > > > Layer > > 2 > > > > (Ethernet, > > > > > > VLAN, etc.) headers, or only Layer 3 (IP) or Layer 4 (TCP, > > > > > > UDP, > > > > etc.)? And how > > > > > > about ARP packets and Layer 2 control protocol packets (STP, > > LACP, > > > > etc.)? > > > > > > > > > > > > > > > > Well, if you append or adjust an odd number of bytes (e.g. a > > > > > PDCP > > > > header) from a previously aligned payload the entire packet will > > then > > > > be unaligned. > > > > > > > > > > > > > If PDCP headers can leave the rest of the packet field unaligned, > > then > > > > we had better remove the alignment restrictions through all of > > DPDK. > > > > > > > > /Bruce > > > > > > Re-reading the details regarding unaligned pointers in C11, as > > > posted > > by Emil > > > in Bugzilla [2], I interpret it as follows: Any 16 bit or wider > > pointer type a must > > > point to data aligned with that type, i.e. a pointer of the type > > "uint16_t *" > > > must point to 16 bit aligned data, and a pointer of the type > > "uint64_t *" must > > > point to 64 bit aligned data. Please, someone tell me I got this > > wrong, and > > > wake me up from my nightmare! > > > > > > Updating DPDK's packet structures to fully support this C11 > > limitation with > > > unaligned access would be a nightmare, as we would need to use byte > > arrays > > > for all structure fields. Functions would also be unable to use > > > other > > pointer > > > types than "void *" and "char *", which seems to be the actual > > problem in > > > the __rte_raw_cksum() function. I guess that it also would prevent > > the > > > compiler from auto-vectorizing the functions. > > > > > > I am usually a big proponent of academically correct solutions, but > > such a > > > change would be too wide ranging, so I would like to narrow it down > > to the > > > actual use case, and perhaps extrapolate a bit from there. > > > > > > @Emil: Do you only need to calculate the checksum of the > > > (potentially > > > unaligned) embedded packet? Or do you also need to use other DPDK > > > functions with the embedded packet, potentially accessing it at an > > unaligned > > > address? > > > > > > I'm trying to determine the scope of this C11 pointer alignment > > limitation for > > > your use case, i.e. whether or not other DPDK functions need to be > > updated > > > to support unaligned packet access too. > > > > > > [2] > > > https://protect2.fireeye.com/v1/url?k=3D31323334-501cfaf3-313273af- > > > 454445554331-2ffe58e5caaeb74e&q=3D1&e=3D3f0544d3-8a71-4676-b4f9- > > > > 27e0952f7de0&u=3Dhttps%3A%2F%2Fbugs.dpdk.org%2Fshow_bug.cgi%3Fid% > > > 3D1035 > > > > That's my interpretation of the standard as well; For example an > > uint16_t* must be on even addresses. If not it is undefined behavior. > > I think this is a bigger problem on ARM for example. > > > > Without being that invested in dpdk, adding unaligned support for > > everything seems like a steep step, but I'm not sure what it entails > > in practice. > > > > We are actually only interested in the checksumming. >=20 > Great! Then we can cancel the panic about rewriting DPDK Core completely. > Although it might still need some review for similar alignment bugs, wher= e > we have been forcing the compiler shut up when trying to warn us. :-) >=20 > I have provided v3 of the patch, which should do as requested - and still= allow > the compiler to auto-vectorize. >=20 > @Emil, will you please test v3 of the patch? It seems to work in these two cases: * Even address, even length * Even address, odd length But it breaks in these two cases: * Odd address, even length (although it works for small buffers, probably w= hen the sum fits inside a uint16_t integer or something) * Odd address, odd length I get (and like) the main idea of the algorithm but haven't yet figured out= what the problem is with odd addresses. /Emil