DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bili Dong <qobilidop@gmail.com>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>
Cc: dev@dpdk.org, cristian.dumitrescu@intel.com
Subject: Re: Question about naive XOR hash in DPDK
Date: Fri, 11 Nov 2022 09:59:57 -0800	[thread overview]
Message-ID: <CAFnY8dFZ6vau_i-CuowE6vC_W5vUbWtRQqSmbZ_s2FoEDZF94A@mail.gmail.com> (raw)
In-Reply-To: <d150d930-dca3-1268-1ebe-2fb6281be527@lysator.liu.se>

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

Hi Mattias,

Maybe an example helps explain this. Here is an example where the CRC hash
function is registered in the DPDK pipeline:
http://git.dpdk.org/dpdk/tree/lib/pipeline/rte_swx_pipeline.c?id=203dcc9cfe4151518bb5a5c59ee22a754e649e35#n10115.
We need something similar to this for the XOR hash. This means we need to
have the XOR hash function implemented somewhere first before we could
register it.

Thanks,
Bili

On Wed, Nov 9, 2022 at 2:08 PM Mattias Rönnblom <hofors@lysator.liu.se>
wrote:

> 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
> >
>

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

      reply	other threads:[~2022-11-11 18:00 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
2022-11-11 17:59   ` Bili Dong [this message]

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=CAFnY8dFZ6vau_i-CuowE6vC_W5vUbWtRQqSmbZ_s2FoEDZF94A@mail.gmail.com \
    --to=qobilidop@gmail.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=hofors@lysator.liu.se \
    /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).