From: Ori Kam <orika@mellanox.com>
To: simei <simei.su@intel.com>,
"qi.z.zhang@intel.com" <qi.z.zhang@intel.com>,
"jingjing.wu@intel.com" <jingjing.wu@intel.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] ethdev: add symmetric toeplitz hash support
Date: Sat, 28 Sep 2019 18:32:04 +0000 [thread overview]
Message-ID: <AM4PR05MB3425B9B0EDCEB498362598CDDB800@AM4PR05MB3425.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1564102511-99609-2-git-send-email-simei.su@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of simei
> Sent: Friday, July 26, 2019 3:55 AM
> To: qi.z.zhang@intel.com; jingjing.wu@intel.com; Adrien Mazarguil
> <adrien.mazarguil@6wind.com>
> Cc: dev@dpdk.org; simei.su@intel.com
> Subject: [dpdk-dev] [PATCH v2 1/2] ethdev: add symmetric toeplitz hash support
>
> From: Simei Su <simei.su@intel.com>
>
> Currently, there are DEFAULT,TOEPLITZ and SIMPLE_XOR hash function.
> To support symmetric hash by rte_flow RSS action, this patch adds
> new hash function "Symmetric Toeplitz" which is supported by some hardware.
>
> Signed-off-by: Simei Su <simei.su@intel.com>
> ---
Acked-by: Ori Kam <orika@mellanox.com>
Thanks,
Ori Kam
> lib/librte_ethdev/rte_flow.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/librte_ethdev/rte_flow.h b/lib/librte_ethdev/rte_flow.h
> index b66bf14..77a0c52 100644
> --- a/lib/librte_ethdev/rte_flow.h
> +++ b/lib/librte_ethdev/rte_flow.h
> @@ -1814,6 +1814,7 @@ enum rte_eth_hash_function {
> RTE_ETH_HASH_FUNCTION_DEFAULT = 0,
> RTE_ETH_HASH_FUNCTION_TOEPLITZ, /**< Toeplitz */
> RTE_ETH_HASH_FUNCTION_SIMPLE_XOR, /**< Simple XOR */
> + RTE_ETH_HASH_FUNCTION_SYMMETRIC_TOEPLITZ, /**< Symmetric
> Toeplitz */
> RTE_ETH_HASH_FUNCTION_MAX,
> };
>
> --
> 1.8.3.1
next prev parent reply other threads:[~2019-09-28 18:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 4:57 [dpdk-dev] [PATCH 0/2] " simei
2019-07-25 4:57 ` [dpdk-dev] [PATCH 1/2] ethdev: " simei
2019-07-31 12:08 ` Andrew Rybchenko
2019-07-31 12:30 ` Adrien Mazarguil
2019-07-31 13:03 ` Andrew Rybchenko
2019-07-31 13:43 ` Shahaf Shuler
2019-09-29 11:51 ` Andrew Rybchenko
2019-09-30 3:12 ` Su, Simei
2019-09-30 6:14 ` Andrew Rybchenko
2019-09-30 6:34 ` Su, Simei
2019-09-30 7:49 ` Zhang, Qi Z
2019-07-25 4:57 ` [dpdk-dev] [PATCH 2/2] app/testpmd: " simei
2019-07-26 0:55 ` [dpdk-dev] [PATCH v2 0/2] " simei
2019-07-26 0:55 ` [dpdk-dev] [PATCH v2 1/2] ethdev: " simei
2019-09-28 18:32 ` Ori Kam [this message]
2019-07-26 0:55 ` [dpdk-dev] [PATCH v2 2/2] app/testpmd: " simei
2019-09-28 18:39 ` Ori Kam
2019-09-24 5:30 ` [dpdk-dev] [PATCH v2 0/2] " Zhang, Qi Z
2019-10-01 9:22 ` [dpdk-dev] [PATCH v3 " Simei Su
2019-10-01 9:22 ` [dpdk-dev] [PATCH v3 1/2] ethdev: " Simei Su
2019-10-01 13:36 ` Andrew Rybchenko
2019-10-01 9:22 ` [dpdk-dev] [PATCH v3 2/2] app/testpmd: " Simei Su
2019-10-01 15:06 ` [dpdk-dev] [PATCH v3 0/2] " Ferruh Yigit
2019-09-23 23:11 ` [dpdk-dev] [PATCH " Zhang, Qi Z
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=AM4PR05MB3425B9B0EDCEB498362598CDDB800@AM4PR05MB3425.eurprd05.prod.outlook.com \
--to=orika@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=simei.su@intel.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).