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 0B99E43355 for ; Fri, 17 Nov 2023 17:22:14 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 04491427D9; Fri, 17 Nov 2023 17:22:14 +0100 (CET) Received: from mail-pf1-f181.google.com (mail-pf1-f181.google.com [209.85.210.181]) by mails.dpdk.org (Postfix) with ESMTP id 74C01411F3 for ; Fri, 17 Nov 2023 17:22:13 +0100 (CET) Received: by mail-pf1-f181.google.com with SMTP id d2e1a72fcca58-6c34e87b571so2012948b3a.3 for ; Fri, 17 Nov 2023 08:22:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1700238132; x=1700842932; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=ixnOKamddRXb1A7/gr4U69zwHaujKTcA5I7UxfK8omM=; b=nHowSswe3PjxbKFUCNDE/apBWsCf57rII2+CZtxnyURpbqzgfUKPuXYq3p3DBePfWI osUz61SPesWM4b7pnCjQNjODqNYF2++NPkENg26p4t8ki2V/aBPVKvl19wqXPRiz9ymI d5rhRRFBMZgnhoefsuMDTT03tnbJ+Wh9uw9c4N4VPmlVSopq6W81b3U7xDewMhW4iQJX Ghgb+JLdzoiGgxnLR2yrq0KG+f60z1MFKjnbWOfRciCSzyhaPt5ht2SkLge4Ebch6219 NrjXoq+D9RnBTrwoSSWRHrXI1HYtLign8GIXaLi6UjdhG1LJcmZmtyqEPGs0iMwgi942 pHig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700238132; x=1700842932; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ixnOKamddRXb1A7/gr4U69zwHaujKTcA5I7UxfK8omM=; b=qwfSwu40C10ca3wx+xdyyZUHY/OUCECnj6LpwIxeTqJlRkvMOWetK5txzoEaifCJ2q LV/QZC2BamegwqFHzXcOmoIKeCedo8xstnSr/DqvKyZcakj6NY9ajXoYH6w3ZJbaRdf4 4K7dNh9CLhYs7ggykgZx6gG7G9MlvyQJ5GdYZIwlkg6p/HIHLdpVwVOFPWMkaNeM79JY eKRDgIdQmwQC2S3qJASmM/rSOPCBmIv4Tx8D3aTWQS08zlDbe1c4Ycep6OpnFEcbGWMw 7oZO50ZfsovpQ0N+CnU/GM2Qfi6JLMjI0jCtsbuJZK9Fk2BrzyXUjoed9qZnKTuyq9E1 9kSw== X-Gm-Message-State: AOJu0Yy3DSVmk34QnuWK0wpm7cPj8SMz/bzU39S3a19xxvVpMsCEk4Y9 azvW0w9RkHr3rHXN9p8vtLU/8Q== X-Google-Smtp-Source: AGHT+IFrxMYbXiandjoEnBkmxfT/iAWJeQ/TDHYbZFU9e/PyOhxqbT97eheKfTlrlyUiyKtHusljTg== X-Received: by 2002:a05:6a20:3c91:b0:187:eb60:d6de with SMTP id b17-20020a056a203c9100b00187eb60d6demr4431005pzj.27.1700238132674; Fri, 17 Nov 2023 08:22:12 -0800 (PST) Received: from hermes.local (204-195-123-141.wavecable.com. [204.195.123.141]) by smtp.gmail.com with ESMTPSA id c5-20020a170902d90500b001bc5dc0cd75sm1561202plz.180.2023.11.17.08.22.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 17 Nov 2023 08:22:12 -0800 (PST) Date: Fri, 17 Nov 2023 08:22:10 -0800 From: Stephen Hemminger To: Ferruh Yigit Cc: Kaiwen Deng , dev@dpdk.org, stable@dpdk.org, qiming.yang@intel.com, yidingx.zhou@intel.com, Aman Singh , Yuying Zhang , Olivier Matz , Pablo de Lara Subject: Re: [PATCH] app/test-pmd: fix L4 checksum with padding data Message-ID: <20231117082210.4d290191@hermes.local> In-Reply-To: <1effba02-7a4c-47bd-8097-a158832c45d7@amd.com> References: <20230804082849.533059-1-kaiwenx.deng@intel.com> <892f0567-e1ee-4283-9726-5db1dd92c2cb@amd.com> <20231116145817.78eb0954@hermes.local> <7a41467c-c863-4ea1-bf7c-9206bf56aa34@amd.com> <20231116192857.0d49ec5b@hermes.local> <1effba02-7a4c-47bd-8097-a158832c45d7@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org On Fri, 17 Nov 2023 09:29:41 +0000 Ferruh Yigit wrote: > >> I agree using 'l3_len' instead is correct fix. > >> > >> But this requires ABI/API change, > >> plus do we have any reason to keep the padding, discarding it as this > >> patch does is also simpler alternative. > > > > > > Possibly an API version to change the args would work to fix. > > > > rte_ipv4_udptcp_cksum_mbuf() and rte_ipv6_udptcp_cksum_mbuf() are inline > functions, unfortunately we can't version them. > > But those functions already gets IP header as parameter, can't we use IP > header to get the payload size? If so this can be fixed without updating > API. Inlines are easier. Just make a fixed new function and make sure the old one is not used. They shouldn't have been inline in the first place.