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 5BF89436F2; Thu, 14 Dec 2023 18:26:13 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 328C94326C; Thu, 14 Dec 2023 18:26:13 +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 64997402C2 for ; Thu, 14 Dec 2023 18:26:12 +0100 (CET) Received: by mail-pl1-f178.google.com with SMTP id d9443c01a7336-1d336760e72so30903325ad.3 for ; Thu, 14 Dec 2023 09:26:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1702574771; x=1703179571; 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=YfB04gJuGuQwre1Wi78TzJbAWIdO7O5DqQEqr42nslk=; b=GNQE9We6AoluuCUUIilFPfwFYC3aJtHRrxyWn+AEW0BEcFiWA5FR6uxZPpyO8nlZkI k6nddIr7UwPXArYqHlTX9JTsvHDWxsfKMlsvnJVza7QbSNbSErEp6W1mIfa6LLom3Fv1 /gTknWaUJiY+Nv+maqLJfDANMdeQzHaLiLzIf2817Fz200OZlWLwRIzd/plESIHGEi70 7bzuqYDBNzEL94eOvXvSYAgDAdZZphY+XovuJKfu89+NfUEeW5b0ghvdZ7f0LN+M6Jh1 N9Yd3w15qy16dqF/X1FXtuIe3lPzNU8gLV+rf+cB9x5aVe1fluv1mmkioZiX57FSQIa+ qBoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702574771; x=1703179571; 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=YfB04gJuGuQwre1Wi78TzJbAWIdO7O5DqQEqr42nslk=; b=UgJyNfmiNU1si/EysWOdiN9JJEdsNOZUlywGaJdve2uiYGEJTREcODKqLT8O57NNTI kRJexJCrbnkC+sV5mvgtTPhrcQ3rOSd3V+unf9L2QZ9VB9xCgwy7BHF+yYnUxU4mmRI8 rDmaYSjKF8dNaGAayps4NWU7EBzZet+2Ppu5T4h7TZcGXIDNbd/NVzP4TJIJR9eAYMyh GqhmVKbAeBSZFVjoeGxyfY+UF4Oo8znBUfd2BbT6P6bISw2QTzUHFIECcDRGlGkCXyDi h04GQTRLqU4MOrso3X5qWcNIhOLYvdV/6A3SmxYvyxxri8+c8LDfCgJ35CZ5yUVwx+pG QcZA== X-Gm-Message-State: AOJu0Yyk4SKjOtK3jUWsfIqnU3jUzwKv3qq0ET7tgja3sv0AiJoXLDwg g0O3+UBYSdFMIeNAGuCwG+ytAQ== X-Google-Smtp-Source: AGHT+IF30x/HMaOz7ewt3V7plVvxoeGC6GrF4Ey5AAnILmKHdrdU0qjmdI3keqAi+GVxR9t5/0hPGg== X-Received: by 2002:a17:902:e883:b0:1d3:4783:cf3 with SMTP id w3-20020a170902e88300b001d347830cf3mr5569976plg.30.1702574771600; Thu, 14 Dec 2023 09:26:11 -0800 (PST) Received: from hermes.local (204-195-123-141.wavecable.com. [204.195.123.141]) by smtp.gmail.com with ESMTPSA id s22-20020a170902989600b001ce5b859a59sm12698430plp.305.2023.12.14.09.26.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 14 Dec 2023 09:26:11 -0800 (PST) Date: Thu, 14 Dec 2023 09:26:09 -0800 From: Stephen Hemminger To: Ori Kam Cc: "Dumitrescu, Cristian" , Ferruh Yigit , Dariusz Sosnowski , "NBU-Contact-Thomas Monjalon (EXTERNAL)" , Andrew Rybchenko , "dev@dpdk.org" , Raslan Darawsheh Subject: Re: [RFC] ethdev: introduce entropy calculation Message-ID: <20231214092609.1b109278@hermes.local> In-Reply-To: References: <20231210083100.7893-1-orika@nvidia.com> <7ec96599-6235-4ef5-9bba-6a037815d358@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 On Thu, 14 Dec 2023 17:18:25 +0000 Ori Kam wrote: > > > Since encap groups number of different 5 tuples together, if HW doesn= =E2=80=99t know > > > how to RSS > > > based on the inner application will not be able to get any distributi= on of =20 > > packets. =20 > > > > > > This value is used to reflect the inner packet on the outer header, s= o =20 > > distribution =20 > > > will be possible. > > > > > > The main use case is, if application does full offload and implements= the encap =20 > > on =20 > > > the RX. > > > For example: > > > Ingress/FDB match on 5 tuple encap send to hairpin / different port = in case of > > > switch. > > > =20 > >=20 > > Smart idea! So basically the user is able to get an idea on how good th= e RSS > > distribution is, correct? > > =20 >=20 > Not exactly, this simply allows the distribution. > Maybe entropy is a bad name, this is the name they use in the protocol, b= ut in reality > this is some hash calculated on the packet header before the encap and se= t in the encap header. > Using this hash results in entropy for the packets. Which can be used for= load balancing. >=20 > Maybe better name would be: > Rte_flow_calc_entropy_hash? >=20 > or maybe rte_flow_calc_encap_hash (I like it less since it looks like we = calculate the hash on the encap data and not the inner part) >=20 > what do you think? Entropy has meaning in crypto and random numbers generators that is differe= nt from this usage. So entropy is bad name to use. Maybe rte_flow_hash_distribution?