From: Jianbo Liu <jianbo.liu@linaro.org>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"jerin.jacob@caviumnetworks.com"
<jerin.jacob@caviumnetworks.com>,
"ashwin.sekhar@caviumnetworks.com"
<ashwin.sekhar@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] examples/ip_pipeline: use crc32 in hash functions for arm64
Date: Wed, 25 Oct 2017 15:01:46 +0800 [thread overview]
Message-ID: <CAP4Qi39g3Bte=WVMWuxG1mEHRqAjGag9vove7YrsOEUU6x+beQ@mail.gmail.com> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891267BAD8DB2@IRSMSX108.ger.corp.intel.com>
On 24 October 2017 at 23:38, Dumitrescu, Cristian
<cristian.dumitrescu@intel.com> wrote:
> Hi Jianbo,
>
> <snip>...
>
>> >> > As mentioned in one of our deprecation notices, I am actively working
>> >> > (not ready for 17.8 unfortunately) to add a key mask parameter to these
>> >> functions, so more work on these hash functions is likely to take place.
>> >>
>
> The above mentioned rework has finally happened, thank you for your patience.
>
> Are you able to rework your patch to accommodate the mask-based hash functions to target the 18.02 release?
>
Sure, I will send a new version.
Thanks!
Jianbo
next prev parent reply other threads:[~2017-10-25 7:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 9:09 Jianbo Liu
2017-07-03 21:11 ` Thomas Monjalon
2017-07-03 23:19 ` Dumitrescu, Cristian
2017-07-03 23:25 ` Thomas Monjalon
2017-07-04 13:55 ` De Lara Guarch, Pablo
2017-07-05 3:38 ` Jianbo Liu
2017-10-24 15:38 ` Dumitrescu, Cristian
2017-10-25 7:01 ` Jianbo Liu [this message]
2017-10-27 9:25 ` [dpdk-dev] [PATCH v2] " Jianbo Liu
2017-10-27 9:55 ` Dumitrescu, Cristian
2017-11-07 7:51 ` Ferruh Yigit
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='CAP4Qi39g3Bte=WVMWuxG1mEHRqAjGag9vove7YrsOEUU6x+beQ@mail.gmail.com' \
--to=jianbo.liu@linaro.org \
--cc=ashwin.sekhar@caviumnetworks.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=thomas@monjalon.net \
/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).