From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Hyong Youb Kim <hyonkim@cisco.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/5] net/enic: add SR-IOV VF representor
Date: Mon, 21 Sep 2020 16:35:24 +0100 [thread overview]
Message-ID: <6c5b7fa8-9378-525c-2770-ab4b5750e961@intel.com> (raw)
In-Reply-To: <20200909135656.18892-1-hyonkim@cisco.com>
On 9/9/2020 2:56 PM, Hyong Youb Kim wrote:
> This series adds VF representors to the driver. It enables
> single-queue representors and implements enough flow features to run
> OVS-DPDK offload for default vlan+mac based switching.
>
> The flow API handlers and devcmd functions (firmware commands) are now
> aware of representors. Representors reserve PF Tx/Rx queues for their
> implicit paths to/from VFs. Packet forwarding rules for these implicit
> paths are set up using firmware's Flow Manager (flowman), which is
> also used for rte_flow API.
>
> Thanks.
> -Hyong
>
> Hyong Youb Kim (5):
> net/enic: extend vnic dev API for VF representors
> net/enic: add minimal VF representor
> net/enic: add single-queue Tx and Rx to VF representor
> net/enic: extend flow handler to support VF representors
> net/enic: enable flow API for VF representor
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-09-21 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 13:56 Hyong Youb Kim
2020-09-09 13:56 ` [dpdk-dev] [PATCH 1/5] net/enic: extend vnic dev API for VF representors Hyong Youb Kim
2020-09-09 13:56 ` [dpdk-dev] [PATCH 2/5] net/enic: add minimal VF representor Hyong Youb Kim
2020-09-09 13:56 ` [dpdk-dev] [PATCH 3/5] net/enic: add single-queue Tx and Rx to " Hyong Youb Kim
2020-09-09 13:56 ` [dpdk-dev] [PATCH 4/5] net/enic: extend flow handler to support VF representors Hyong Youb Kim
2020-09-09 13:56 ` [dpdk-dev] [PATCH 5/5] net/enic: enable flow API for VF representor Hyong Youb Kim
2020-09-21 15:35 ` Ferruh Yigit [this message]
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=6c5b7fa8-9378-525c-2770-ab4b5750e961@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hyonkim@cisco.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).