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 41EC542B27; Tue, 16 May 2023 19:32:50 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1AA6A406B6; Tue, 16 May 2023 19:32:50 +0200 (CEST) Received: from mail-wm1-f49.google.com (mail-wm1-f49.google.com [209.85.128.49]) by mails.dpdk.org (Postfix) with ESMTP id 067114003C for ; Tue, 16 May 2023 19:32:49 +0200 (CEST) Received: by mail-wm1-f49.google.com with SMTP id 5b1f17b1804b1-3f2548256d0so3805e9.1 for ; Tue, 16 May 2023 10:32:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1684258368; x=1686850368; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Oilq35aLZDugGalWbTypRIAYbhb2kw03p0ePmQmRNDo=; b=Twuw0d9V8aH4DYdEMREocZTASvw3nGx6IpHjNpnQbhPRsHrC+2xlKMrbtb0sfjaxkp UeHNFE18C5GCCH8k6GEgoIxEBAsOUvxN15D265GmsBUxGMPbMvXV+itbErurRptbO6Q8 Xmt+ajvTbXl48/nWu2hER1wUcCqPkqqrKl+TnZ0hDsgYUstqnYtB/fKNpqwQywgqBXw7 RZUuSawfL0wVYXjRw0V5au5Iv5KDHSB3bjjshqcr5Tx5QC4Eh3lLlrAqvHzNeli7e3TS 7VQnB6F52yZGuKcCAkTWxzMHBb+f6OmPRHrFssAMtrfHxhYnxJ1qX9/mNB/ceNa7cIQ5 aG4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684258368; x=1686850368; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Oilq35aLZDugGalWbTypRIAYbhb2kw03p0ePmQmRNDo=; b=bmG2P3lQs3Jfb0Fq8DvxGzedvADnUQGe1dsr4r97M66pHAYbs4iUOPq2IVyyTZgJbf bAQ3saIHiP6R6tEpOio3vb62zvqLM/QuDyefsAgciKvAshijKZPd2BZlPhejqSr/La80 pU7J19cv5/HoX20kAlTSegnL/e90ZWzDjwjReQsDOmDb+gAbJPSPZmuZRnNI7dY7zPD9 fO23UiBeVlBsw1wjvEIGDYFdD/QEkintcUVwpkyRivMb/jv3pJzoErJU8tdNzes2wQOa CiKGbm+MQqJA+lAN0/JdgellBdVxJ2sPxtEfGaYLFeHvU0wajGbXxHy4HzVAxxRHtyoQ WhPw== X-Gm-Message-State: AC+VfDwaTkOQnA3qfSjKnBjQGmn64ozf34iSeBqA9KfuBzPH2Y+Jinu9 M+Puz32Mf5l3mHs/wx+irgUuWZhZBHKRq0do+3z01g== X-Google-Smtp-Source: ACHHUZ5Btx3Dob5ozuNqJ3FhuGUfQEr8BKnqTjRPRGGJ+duGkUAYjE2F8rliQDMx5Lq4nMPvzGNrdg6xdYFHj0JinZQ= X-Received: by 2002:a05:600c:1ca0:b0:3f1:9396:6fbf with SMTP id k32-20020a05600c1ca000b003f193966fbfmr3293wms.4.1684258368548; Tue, 16 May 2023 10:32:48 -0700 (PDT) MIME-Version: 1.0 References: <20230412181619.496342-1-joshwash@google.com> <20230421232022.342081-1-joshwash@google.com> <6c4b95ca-48f3-d1e2-7b39-c1c251095493@amd.com> In-Reply-To: <6c4b95ca-48f3-d1e2-7b39-c1c251095493@amd.com> From: Joshua Washington Date: Tue, 16 May 2023 10:32:37 -0700 Message-ID: Subject: Re: [PATCH v5] app/testpmd: txonly multiflow port change support To: Ferruh Yigit Cc: Aman Singh , Yuying Zhang , dev@dpdk.org, Rushil Gupta , Stephen Hemminger Content-Type: multipart/alternative; boundary="000000000000c55c4305fbd2f5c9" 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 --000000000000c55c4305fbd2f5c9 Content-Type: text/plain; charset="UTF-8" Hello, I believe my original solution was something closer to what you are suggesting for backward compatibility. I originally had a flag that enabled changing source port instead of source IP addresses, but I received feedback that adding an extra flag was complicating things too much from Stephen. On a VM, the purpose of using multi-flow is similar to that of bare metal: to test RSS in the RX side. However, generating traffic by changing source IP address can cause inconsistencies in performance due to protections in cloud infrastructure from sending packets from a different source IP address than is provisioned for the VM. Changing source UDP port to test RSS should be functionally equivalent while allowing VMs to send traffic from a single source IP address. If everyone agrees that adding --txonly-multi-flow as an option as well as keeping the flag is an acceptable way of moving forward, I can do that. Thanks, Josh --000000000000c55c4305fbd2f5c9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

I believe=C2=A0= my original solution was something closer to what you are suggesting for ba= ckward compatibility. I originally had a flag that enabled changing source = port instead of source IP addresses, but I received feedback that adding an= extra flag was complicating things too much from Stephen.

On a VM, the purpose of using multi-flow is similar to that of bar= e metal: to test RSS in the RX side. However, generating traffic by changin= g source IP address can cause inconsistencies in performance=C2=A0due to pr= otections in cloud infrastructure from sending packets from a different sou= rce IP address than is provisioned for the VM. Changing source UDP port to = test RSS should be functionally equivalent while allowing VMs to send traff= ic from a single source IP address.

If everyone ag= rees that adding --txonly-multi-flow as an option as well as keeping the fl= ag is an acceptable=C2=A0way of moving forward, I can do that.
Thanks,
Josh
=C2=A0
--000000000000c55c4305fbd2f5c9--