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 2ED3D41B93 for ; Tue, 31 Jan 2023 22:40:06 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B5C7340684; Tue, 31 Jan 2023 22:40:05 +0100 (CET) Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) by mails.dpdk.org (Postfix) with ESMTP id B864B4067B for ; Tue, 31 Jan 2023 22:40:04 +0100 (CET) Received: by mail-pl1-f178.google.com with SMTP id jh15so7432345plb.8 for ; Tue, 31 Jan 2023 13:40:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; 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=fZq8lGmcO+FJjj02E+w9s4B39wwNpqEUxjI+sK9JkSM=; b=a7xPbG599GTGkgmtk3j8pLHWrzOpNPDAPh+8iKtWeV1UzMtsdsv2yvncEMdxCoL+XT bJysZwmw1kcXNYbN5WR+vnWjqgvNCDqIGmQgWfiNL2jkV/+YA+wtsRTFs4kQ1VZzHOmu S84gLQiE/A4kihaR31bSw4yuVmJZ2YkLhifpysePEfKMy/L9MAyZt6OOsuARsgyaWI8C r+cADBoO1o7pTtfoJdeDikH5d5olWa5Mt0m9y8A77G3GybyeEQDfEmYovZfjBajXiASD xnV1gqYyPlmNNt8SaqwsoC+ej6lZgi2Xn+KbwUeaD0jyUdZ6NNmEJB97ik7S5yKs44zz 1crg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=fZq8lGmcO+FJjj02E+w9s4B39wwNpqEUxjI+sK9JkSM=; b=ojvNGcn5tRVZzDx+ZnT+387nCPKVWVtKg7JTcA6yRHO2iradgI6TpDoyeMHaAUHEV+ sJxLz5wUzN9n3H5NSN80uZbDzzq49Il+U1G5O3XopS8mkny35K13/VdHakwNYB5v4T6Q knXcJ9CqDQUfpsyPI2Wnx8rIR/IP/B648Y4jN3sEHgYP/+UDWmRddLi8So1T7cfS94u5 piye4QP7MlJVYy4xWwQTQvwC5uI4JpE1O7P8RPGh9r67mho9w86mZzWI0eb/IDQtUKgg xnPp8rcT89PO0qMhG8JO5YkzIqKiwp0qAfiCTwkJCAGyOFaald2gDKtnsp6xDLB5eUI1 lI0w== X-Gm-Message-State: AO0yUKXamiz2yVbRr9yZVkyT2Do8xbFWqCus92gniy/dQ/6mBAoaYN+5 NsqGazHLmxZpVDpORvtMteEvNA== X-Google-Smtp-Source: AK7set/kFz2BYwqdY+6YR3yzl4ejknWjh/J4TS7TL0dsMhkuhu2eWirBE56AaE9YqgOzmI6402Z49Q== X-Received: by 2002:a17:90a:19cb:b0:229:6b20:2424 with SMTP id 11-20020a17090a19cb00b002296b202424mr14919210pjj.11.1675201203847; Tue, 31 Jan 2023 13:40:03 -0800 (PST) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id h4-20020a17090a648400b00229f0c629e1sm8977898pjj.45.2023.01.31.13.40.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 31 Jan 2023 13:40:03 -0800 (PST) Date: Tue, 31 Jan 2023 13:40:01 -0800 From: Stephen Hemminger To: "Joshi, Venkatesh" Cc: "users@dpdk.org" Subject: Re: Flexible payload feature of i40e PMD in DPDK 20.11 Message-ID: <20230131134001.522b20c3@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Tue, 31 Jan 2023 18:44:51 +0000 "Joshi, Venkatesh" wrote: > Hi, > > I have the following configuration: > > NIC: Intel XXV710 (supported by i40e PMD) > DPDK version: 20.11 > > My requirement is to use Flexible payload of the XXV710 NIC (i40e PMD) to do the following: > > * For incoming packets where the ethertype is 0x0806 (ie: ARP packets), do the RSS hashing based on the Sender Hardware Address instead of the ethertype field which is considered by default. > * Basically, I don't want all the ARP packets falling on the same queue. Hence, hashing based on the sender hardware address would give a good distribution across multiple CPUs where my dpdk application is running. > > > However, I have not been able to find any examples where the following macros have been used - RTE_ETH_INPUT_SET_FLEX_PAYLOAD_1ST_WORD through RTE_ETH_INPUT_SET_FLEX_PAYLOAD_8TH_WORD. > > > Any pointers would be much appreciated. The old flow direct stuff is deprecated. What you want could be done via rte_flow API by defining a match for ARP (ethertype) and action of rte_eth_flow_action_rss of type L2_PAYLOAD and pointing at the sender. But that assumes the i40e driver implements all this and it doesn't. You probably have to live will ARP arriving on single queue and do any fanout you want using rte_ring's.