From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7ED18A00C2; Mon, 15 Aug 2022 17:45:37 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 678E840146; Mon, 15 Aug 2022 17:45:37 +0200 (CEST) Received: from mail-pj1-f43.google.com (mail-pj1-f43.google.com [209.85.216.43]) by mails.dpdk.org (Postfix) with ESMTP id 29C4C40143 for <dev@dpdk.org>; Mon, 15 Aug 2022 17:45:36 +0200 (CEST) Received: by mail-pj1-f43.google.com with SMTP id q7-20020a17090a7a8700b001f300db8677so7074896pjf.5 for <dev@dpdk.org>; Mon, 15 Aug 2022 08:45:36 -0700 (PDT) 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:to:from:date:from:to:cc; bh=/MScZLgusSaVZMKAiefMMic9hGC0LBT5kaWP0OU97Ko=; b=06HpPXyK89qjmkE1Jl2PDApHiR17hM/Ric73j9f/FUx4DK92cANNHp09y4yombdPAj 0qOs4Gl3sNwT2pci6IYLAnfobQFz1FRHCXKV9WChVK6knQ6V7vRArWA5g3l5icVudbVL XjMZT1X6ke1r3T/ofM+lbcvs2fIXvx1AP/YC66ZXgSsq/v49KReZxsdYzrD1qw5eg2bo bS0sbSF3+SBIC4IWCm4i3orWvf0Ocjpam/oMQcyEA6CSO+EVpPhECUiGhkcxjfrZ25cm Ke2wl5y/XbiHMnGj4+4n9MTRW0dJUo9LqfdGtgtmPv6aOrLuAyH1Qfu6wO3EFDuK6EG9 qYQA== 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:to:from:date:x-gm-message-state:from:to:cc; bh=/MScZLgusSaVZMKAiefMMic9hGC0LBT5kaWP0OU97Ko=; b=pf5Aap0HijSSyz/eIuZ3Na6z/VB9LRJ/wwhDFs+Ovw0Uhc6ahoonmRJ0zsuRbyEKCd P6ahMwYIf0X5XmodnhqL+oTOeE8JwREZ7zJNKPg1yXtXv+LmqOJhAuDUqAijEsHJaelp XhEeNCilH7gUREj/sQ17Bl3/EXHGKIttGxLSnGZcgWC043gmSrCToU0hc1z/6QV5pFWa lFg1cxgKOVFxVlTh/G1nsfWKXyx9uEOxAKzKLxBjU0RWyUck52bWI6k3x/9z7cJaq3jI C+OKdDqIug60heWyJeUOkEztnHtnfwQ4Gf/ZmFnrXdG5F51M2x1DlE+hk2P2o7ZpXcAE LOow== X-Gm-Message-State: ACgBeo09wQcxMEO6WHDS1qpua5AZPRXTrMmppMV8xsbSAJj4m4l175BJ 9El+lc8XPEd2du4fib7NevxCHxHaLlHLZA== X-Google-Smtp-Source: AA6agR4Tg2DrXo20m4mSzNJe9t76tedlaylkxcqIqg4S73rL9psr9jbClq7uvoAp4wuIgZpIBBb6PA== X-Received: by 2002:a17:90b:3502:b0:1f3:550:5f6f with SMTP id ls2-20020a17090b350200b001f305505f6fmr19266643pjb.49.1660578335115; Mon, 15 Aug 2022 08:45:35 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id s65-20020a625e44000000b0052c87380aebsm6716856pfb.1.2022.08.15.08.45.34 for <dev@dpdk.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 15 Aug 2022 08:45:34 -0700 (PDT) Date: Mon, 15 Aug 2022 08:45:33 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: dev@dpdk.org Subject: Re: [RFC] pcapng: record received RSS hash in pcap file Message-ID: <20220815084533.3a94f286@hermes.local> In-Reply-To: <20220726213618.142173-1-stephen@networkplumber.org> References: <20220726213618.142173-1-stephen@networkplumber.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org On Tue, 26 Jul 2022 14:36:19 -0700 Stephen Hemminger <stephen@networkplumber.org> wrote: > There is an option for recording RSS hash with packets in the > pcapng standard. This implements this for all received packets. > > There is a corner case that can not be addressed with current > DPDK API's. If using rte_flow() and some hardware it is possible > to write a flow rule that uses another hash function like XOR. > But there is no API that records this, or provides the algorithm > info on a per-packet basis. > > The current version of wireshark does not display the recorded > hash option. But if we build it they will come. > Wireshark support for displaying RSS hash is now in a pull request.