From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Bly, Mike" <mbly@ciena.com>,
"Yeddula, Avinash" <ayeddula@ciena.com>,
"dev@dpdk.org" <dev@dpdk.org>, dev <dev-bounces@dpdk.org>,
"users@dpdk.org" <users@dpdk.org>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Laatz, Kevin" <kevin.laatz@intel.com>
Subject: Re: [dpdk-dev] 17.05 --> 17.11, minimum hash table key size
Date: Mon, 2 Jul 2018 09:33:27 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E762F2C@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CY1PR04MB20573068762B33C15EE7C8ACCF4E0@CY1PR04MB2057.namprd04.prod.outlook.com>
> -----Original Message-----
> From: Bly, Mike [mailto:mbly@ciena.com]
> Sent: Friday, June 29, 2018 9:01 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Yeddula, Avinash
> <ayeddula@ciena.com>; dev@dpdk.org; dev <dev-bounces@dpdk.org>;
> users@dpdk.org
> Subject: RE: 17.05 --> 17.11, minimum hash table key size
>
> Cristian,
>
> Thank you. I have done the recommended change. The next thing we have
> run into is the f_hash selection. We were historically using
> rte_hash_crc_8byte() from rte_has_crc.h. In looking at DPDK content, I do
> not see anything close in an rte_*.h file to use with the appropriate input
> parameter list. I did find use of hash_default_key8() in
> examples/ip_pipeline/pipeline/hash_func.h. Is there no formal rte_*.h
> replacement/update for this relative to the hash-table changes in 17.11+? Is
> the expectation that the implementer will create their own as done with the
> aforementioned ip_pipeline example?
>
> -MikeB
>
Hi Mike,
Yes, we are working to move the code from examples/ip_pipeline/hash_func.h into librte_table, Kevin is working on it right now.
Regards,
Cristian
next prev parent reply other threads:[~2018-07-02 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 0:10 Yeddula, Avinash
2018-06-29 11:17 ` Dumitrescu, Cristian
2018-06-29 20:00 ` Bly, Mike
2018-07-02 9:33 ` Dumitrescu, Cristian [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-29 0:03 Bly, Mike
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=3EB4FA525960D640B5BDFFD6A3D891268E762F2C@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=ayeddula@ciena.com \
--cc=dev-bounces@dpdk.org \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=kevin.laatz@intel.com \
--cc=mbly@ciena.com \
--cc=users@dpdk.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 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).