From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ophir Munk <ophirmu@mellanox.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>
Cc: Asaf Penso <asafp@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Olga Shern <olgas@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v1] ethdev: document RSS default key and types
Date: Mon, 5 Nov 2018 13:11:02 +0000 [thread overview]
Message-ID: <b82bb0c8-7486-f07f-5dfc-fc552496d07c@intel.com> (raw)
In-Reply-To: <1541259953-4273-1-git-send-email-ophirmu@mellanox.com>
On 11/3/2018 3:46 PM, Ophir Munk wrote:
> struct rte_flow_action_rss include fields 'key' and 'types'.
> Field 'key' is a pointer to bytes array (uint8_t *) which contains the
> specific RSS hash key.
> If an application is only interested in default RSS operation it
> should not care about the specific hash key. The application can set
> the hash key to NULL such that any PMD uses its default RSS key.
>
> Field 'types' is a uint64_t bits flag used to specify a specific RSS
> hash type such as ETH_RSS_IP (see ETH_RSS_*).
> If an application does not care about the specific RSS type it can set
> this field to 0 such that any PMD uses its default type.
>
> Signed-off-by: Ophir Munk <ophirmu@mellanox.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2018-11-05 13:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 15:46 Ophir Munk
2018-11-05 13:11 ` Ferruh Yigit [this message]
2018-11-05 21:47 ` Thomas Monjalon
2018-11-07 9:23 ` [dpdk-dev] [PATCH v2] " Ophir Munk
2018-11-07 9:31 ` Adrien Mazarguil
2018-11-07 12:39 ` Ophir Munk
2018-11-07 14:06 ` Adrien Mazarguil
2018-11-07 15:13 ` Ophir Munk
2018-11-07 16:41 ` Adrien Mazarguil
2018-11-08 6:32 ` Andrew Rybchenko
2018-11-08 8:50 ` Ophir Munk
2018-11-08 23:07 ` Yongseok Koh
2018-11-09 8:13 ` Ophir Munk
2018-11-11 9:35 ` Ori Kam
2018-11-13 17:15 ` Adrien Mazarguil
2018-11-13 18:04 ` Ophir Munk
2018-11-13 18:39 ` Shahaf Shuler
2018-11-14 9:40 ` Adrien Mazarguil
2018-11-14 13:51 ` Shahaf Shuler
2018-11-14 15:16 ` Adrien Mazarguil
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=b82bb0c8-7486-f07f-5dfc-fc552496d07c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.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).