All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Magistro <koncept1@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [RFC] pcapng: record received RSS hash in pcap file
Date: Tue, 25 Oct 2022 14:01:04 -0400	[thread overview]
Message-ID: <CAKx8PBhwBvN84Q1xONWa_sPnKm_Aza80+rrY4F6Tj0LtX1SiNg@mail.gmail.com> (raw)
In-Reply-To: <20221021130525.46732044@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

Tested with Wireshark 4.1.0rc0-599-g708da4852678 (and older version to
confirm no issues)

Tested-by: Ben Magistro <koncept1@gmail.com>

On Fri, Oct 21, 2022 at 4:05 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:

> 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.
>
> Support for displaying RSS hash in record has been merged into
> Wireshark for 4.1 release.
>
> Could this please be acked and merged.
>

[-- Attachment #2: Type: text/html, Size: 1564 bytes --]

  reply	other threads:[~2022-10-25 18:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 21:36 [RFC] pcapng: record received RSS hash in pcap file Stephen Hemminger
2022-08-15 15:45 ` Stephen Hemminger
2022-10-21 20:05 ` Stephen Hemminger
2022-10-25 18:01   ` Ben Magistro [this message]
2022-10-27  8:29 ` David Marchand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKx8PBhwBvN84Q1xONWa_sPnKm_Aza80+rrY4F6Tj0LtX1SiNg@mail.gmail.com \
    --to=koncept1@gmail.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.