From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ophir Munk <ophirmu@mellanox.com>,
dev@dpdk.org, Pascal Mazon <pascal.mazon@6wind.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Olga Shern <olgas@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/tap: report on supported RSS hash functions
Date: Thu, 10 May 2018 21:13:02 +0100 [thread overview]
Message-ID: <4a27ee61-f5ef-c81c-1c48-b83131bd5d80@intel.com> (raw)
In-Reply-To: <1525973225-28617-1-git-send-email-ophirmu@mellanox.com>
On 5/10/2018 6:27 PM, Ophir Munk wrote:
> Report on TAP supported RSS functions as part of dev_infos_get
> callback: ETH_RSS_IP, ETH_RSS_UDP and ETH_RSS_TCP.
> Known limitation: TAP supports all of the above hash functions together
> and not in partial combinations.
> Previous to this commit RSS support was reported as none. Since the
> introduction of [1] it is required that all RSS configurations will be
> verified.
>
> [1] commit 8863a1fbfc66 ("ethdev: add supported hash function check")
>
> Signed-off-by: Ophir Munk <ophirmu@mellanox.com>
> ---
> v1:
> Initial release
> v2:
> fix checkpach warnings
Hi Ophir,
This patch has been sent after it has been applied. v2 was applied and this is
also v2, and as far as I can see there is no change so I assume this has been
sent by mistake, if not please shout.
next prev parent reply other threads:[~2018-05-10 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 16:51 [dpdk-dev] [PATCH v1] " Ophir Munk
2018-05-08 17:07 ` [dpdk-dev] [PATCH v2] " Ophir Munk
2018-05-09 22:19 ` Ferruh Yigit
2018-05-09 22:22 ` Ferruh Yigit
2018-05-10 17:27 ` Ophir Munk
2018-05-10 20:13 ` Ferruh Yigit [this message]
2018-05-10 22:05 ` Ophir Munk
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=4a27ee61-f5ef-c81c-1c48-b83131bd5d80@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=pascal.mazon@6wind.com \
--cc=shahafs@mellanox.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).