From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Bly, Mike" <mbly@ciena.com>
Subject: Re: [dpdk-dev] DPDK hash function related question
Date: Wed, 23 Sep 2015 12:47:49 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126478D6D05@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <10949795.PKElVBY67L@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, September 22, 2015 4:41 PM
> To: Dumitrescu, Cristian
> Cc: dev@dpdk.org; Yeddula, Avinash; Bly, Mike
> Subject: Re: [dpdk-dev] DPDK hash function related question
>
> 2015-09-22 10:05, Dumitrescu, Cristian:
> > Are you using a DPDK release older than 2.1?
> > In DPDK we moved away from test_hash to CRC-based hashes.
> > Please take a look at DPDK release 2.1 examples/ip_pipeline application:
> > in pipeline_flow_classification_be.c, we use CRC-based hash functions
> > defined in file hash_func.h from the same folder.
>
> Has it already been said that these functions should be hosted elsewhere?
> e.g in librte_hash ;)
It is fine with me. Pablo, feel free to look at these functions and move them to librte_hash if useful.
We are looking to augment these functions to with some more for symmetric hashing during 2.2 (hopefully) or 2.3 development, might be better to wait for this until that time for a more comprehensible solution.
Regards,
Cristian
next prev parent reply other threads:[~2015-09-23 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 22:34 Yeddula, Avinash
2015-09-22 10:05 ` Dumitrescu, Cristian
2015-09-22 13:40 ` Thomas Monjalon
2015-09-23 12:47 ` Dumitrescu, Cristian [this message]
2015-10-12 17:03 ` Yeddula, Avinash
2015-10-13 8:05 ` De Lara Guarch, Pablo
2015-10-13 11:44 ` Dumitrescu, Cristian
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=3EB4FA525960D640B5BDFFD6A3D89126478D6D05@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=mbly@ciena.com \
--cc=thomas.monjalon@6wind.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).