From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Eduard Serra Miralles <eserra@vmware.com>,
Yong Wang <yongwang@vmware.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/vmxnet3: v4 boot and guest UDP RSS configuration
Date: Fri, 19 Apr 2019 11:15:06 +0100 [thread overview]
Message-ID: <fef59b14-93dc-0e1a-825f-a33a12816a05@intel.com> (raw)
Message-ID: <20190419101506.tJgGYa51RTbGqAj3ssGriHhY86P27rvyovv7Cy-Qtgs@z> (raw)
In-Reply-To: <1555621175-103437-1-git-send-email-eserra@vmware.com>
On 4/18/2019 9:59 PM, Eduard Serra Miralles wrote:
> From: Eduard Serra <eserra@vmware.com>
>
> This patch introduces:
> - VMxnet3 v4 negotiation and,
> - entirely guest-driven UDP RSS support.
>
> VMxnet3 v3 already has UDP RSS support, however it
> depends on hypervisor provisioning on the VM through
> ESX specific flags, which are not transparent or known
> to the guest later on.
>
> Vmxnet3 v4 introduces a new API transaction which allows
> configuring RSS entirely from the guest. This API must be
> invoked after device shared mem region is initialized.
>
> IPv4 ESP RSS (SPI based) is also available, but currently
> there are no ESP RSS definitions on rte_eth layer to
> handle that.
>
> Signed-off-by: Eduard Serra <eserra@vmware.com>
> Acked-by: Yong Wang <yongwang@vmware.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-04-19 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 20:59 Eduard Serra Miralles
2019-04-18 20:59 ` Eduard Serra Miralles
2019-04-19 10:15 ` Ferruh Yigit [this message]
2019-04-19 10:15 ` 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=fef59b14-93dc-0e1a-825f-a33a12816a05@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=eserra@vmware.com \
--cc=yongwang@vmware.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).