From: Alex Rosenbaum <rosenbaumalex@gmail.com>
To: Qi Zhang <qi.z.zhang@intel.com>
Cc: adrien.mazarguil@6wind.com, DPDK <dev@dpdk.org>,
Declan Doherty <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [RFC v2 0/5] rte_flow extension for vSwitch acceleration
Date: Thu, 21 Dec 2017 15:01:36 +0200 [thread overview]
Message-ID: <CAFgAxU-+Qju825+aiW4S1KX60ox8PWdQNQgLwg6gC9i7e9riQA@mail.gmail.com> (raw)
In-Reply-To: <1513823719-36066-1-git-send-email-qi.z.zhang@intel.com>
On Thu, Dec 21, 2017 at 4:35 AM, Qi Zhang <qi.z.zhang@intel.com> wrote:
> This patch extend rte_flow API.
> The purpose is to provide comfortable programming interface for virtual switch
> software (such as OVS) to take advantage of incoming device's vSwitch acceleration
> capability when using DPDK as data plane.
>
> Below is summary of changes:
>
> 1. Support to specify flow's destination as an ethdev interface.
>
> Add action RTE_FLOW_ACTION_TYPE_ETHDEV_PORT, use port_id as the identification
> of the destitation. A typical use case is, with a smart NIC used for vSwitch
> acceleration, flow is defined to redirect packet between switch port that is
> managed by a Port Representor.
> See patch for Port Representor: http://dpdk.org/dev/patchwork/patch/31458/
If we are going to have a representation of a switch in DPDK then I we
need real PMD's for the switch ports, and not virtual PMD's as in the
Port Representor model.
These real ports will probably require specific switch_ops, which are
different than the NIC (eth_dev_ops). At least few additional on top
of NIC ops.
We will need to support Tx and Rx burst on these switch ports and
configure ACL's, flooding mode and more.
Alex
prev parent reply other threads:[~2017-12-21 13:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 2:35 Qi Zhang
2017-12-21 2:35 ` [dpdk-dev] [RFC v2 1/5] ether: add flow action to redirect packet in a switch domain Qi Zhang
2017-12-21 12:37 ` Alex Rosenbaum
2017-12-22 8:20 ` Zhang, Qi Z
2017-12-22 22:10 ` Alex Rosenbaum
2017-12-21 2:35 ` [dpdk-dev] [RFC v2 2/5] ether: add flow last hit query support Qi Zhang
2017-12-21 2:35 ` [dpdk-dev] [RFC v2 3/5] ether: Add flow timeout support Qi Zhang
2017-12-21 13:59 ` Alex Rosenbaum
2017-12-22 9:03 ` Zhang, Qi Z
2017-12-22 14:06 ` Wiles, Keith
2018-01-14 2:03 ` Zhang, Qi Z
2017-12-22 22:26 ` Alex Rosenbaum
2017-12-26 3:28 ` Zhang, Qi Z
2017-12-26 7:44 ` Alex Rosenbaum
2017-12-21 2:35 ` [dpdk-dev] [RFC v2 4/5] ether: add more protocol support in rte_flow Qi Zhang
2017-12-21 2:35 ` [dpdk-dev] [RFC v2 5/5] ether: add packet modification aciton " Qi Zhang
2017-12-21 13:01 ` Alex Rosenbaum [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=CAFgAxU-+Qju825+aiW4S1KX60ox8PWdQNQgLwg6gC9i7e9riQA@mail.gmail.com \
--to=rosenbaumalex@gmail.com \
--cc=adrien.mazarguil@6wind.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@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).