DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mattias Rönnblom" <hofors@lysator.liu.se>
To: Bili Dong <qobilidop@gmail.com>, dev@dpdk.org
Cc: cristian.dumitrescu@intel.com
Subject: Re: Question about naive XOR hash in DPDK
Date: Wed, 9 Nov 2022 23:08:41 +0100	[thread overview]
Message-ID: <d150d930-dca3-1268-1ebe-2fb6281be527@lysator.liu.se> (raw)
In-Reply-To: <CAFnY8dEX_KXS=oRkOR=U0DJSKzk_bp5gKmRAw--z_sU+ELU__Q@mail.gmail.com>

On 2022-11-07 19:57, Bili Dong wrote:
> Dear DPDK devs,
> 
> We are using DPDK as the backend target of a P4 pipeline 
> (https://github.com/p4lang/p4-dpdk-target 
> <https://github.com/p4lang/p4-dpdk-target>). A recent issue we are 
> trying to solve is to support a naive XOR hash (something like this 
> <https://github.com/p4lang/behavioral-model/blob/b7a5c105e5c21414ac07f7f2879b45c000ab2aa4/src/bm_sim/calculations.cpp#L380-L399>) in this pipeline. This requires an XOR hash implementation in DPDK.I have the following questions:


Why would it *require* an xor hash function in DPDK?

> 
>  1. Is there already an XOR hash implementation in DPDK? I haven't found
>     it myself, but I could have missed it.
>  2. If it doesn't exist, I'm willing to contribute one, as the
>     implementation is quite straightforward. But I might need your help
>     on where to put the code, as I'm not that familiar with the code
>     organization.
> 
> Any help would be appreciated!
> 
> Thanks,
> Bili
> 

  reply	other threads:[~2022-11-09 22:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 18:57 Bili Dong
2022-11-09 22:08 ` Mattias Rönnblom [this message]
2022-11-11 17:59   ` Bili Dong

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=d150d930-dca3-1268-1ebe-2fb6281be527@lysator.liu.se \
    --to=hofors@lysator.liu.se \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=qobilidop@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).