From: "Wiles, Keith" <keith.wiles@intel.com>
To: Pascal Mazon <pascal.mazon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] net/tap: remote netdevice traffic capture
Date: Fri, 3 Mar 2017 15:54:52 +0000 [thread overview]
Message-ID: <33A6CFE9-FE2E-444F-9333-309D32EE70FD@intel.com> (raw)
In-Reply-To: <cover.1488542158.git.pascal.mazon@6wind.com>
> On Mar 3, 2017, at 6:27 AM, Pascal Mazon <pascal.mazon@6wind.com> wrote:
>
> This patchset adds the special "remote" feature to the tap PMD, that
> actually enables capturing traffic from another netdevice. This is
> especially useful to get packets into the DPDK app, when the remote
> netdevice has no DPDK support.
>
> The "remote" feature requires flow API support as flow rules will be
> configured on the remote netdevice for redirection, using the same
> mechanism.
>
> This series applies on top of:
>
> [PATCH 0/4] net/tap: support flow API
>
> Pascal Mazon (4):
> net/tap: add remote netdevice traffic capture
> net/tap: reflect tap flags on the remote
> net/tap: use the remote MAC address if available
> net/tap: set MTU on the remote
>
> doc/guides/nics/tap.rst | 17 ++
> drivers/net/tap/rte_eth_tap.c | 212 ++++++++++++++++++---
> drivers/net/tap/tap.h | 4 +
> drivers/net/tap/tap_flow.c | 414 ++++++++++++++++++++++++++++++++++++++++--
> drivers/net/tap/tap_flow.h | 24 +++
> 5 files changed, 631 insertions(+), 40 deletions(-)
Ah here is the tap.rst change, thanks.
>
> --
> 2.8.0.rc0
>
Regards,
Keith
next prev parent reply other threads:[~2017-03-03 15:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 12:27 Pascal Mazon
2017-03-03 12:27 ` [dpdk-dev] [PATCH 1/4] net/tap: add " Pascal Mazon
2017-03-03 12:27 ` [dpdk-dev] [PATCH 2/4] net/tap: reflect tap flags on the remote Pascal Mazon
2017-03-03 12:27 ` [dpdk-dev] [PATCH 3/4] net/tap: use the remote MAC address if available Pascal Mazon
2017-03-03 12:27 ` [dpdk-dev] [PATCH 4/4] net/tap: set MTU on the remote Pascal Mazon
2017-03-03 15:54 ` Wiles, Keith [this message]
2017-03-07 16:38 ` [dpdk-dev] [PATCH v2 0/4] remote netdevice traffic capture Pascal Mazon
2017-03-07 16:38 ` [dpdk-dev] [PATCH v2 1/4] net/tap: add " Pascal Mazon
2017-03-07 16:38 ` [dpdk-dev] [PATCH v2 2/4] net/tap: reflect tap flags on the remote Pascal Mazon
2017-03-07 16:38 ` [dpdk-dev] [PATCH v2 3/4] net/tap: use the remote MAC address if available Pascal Mazon
2017-03-07 16:38 ` [dpdk-dev] [PATCH v2 4/4] net/tap: set MTU on the remote Pascal Mazon
2017-03-08 10:06 ` [dpdk-dev] [PATCH v3 0/4] net/tap: remote netdevice traffic capture Pascal Mazon
2017-03-08 10:06 ` [dpdk-dev] [PATCH v3 1/4] net/tap: add " Pascal Mazon
2017-03-08 10:06 ` [dpdk-dev] [PATCH v3 2/4] net/tap: reflect tap flags on the remote Pascal Mazon
2017-03-08 10:06 ` [dpdk-dev] [PATCH v3 3/4] net/tap: use the remote MAC address if available Pascal Mazon
2017-03-08 10:06 ` [dpdk-dev] [PATCH v3 4/4] net/tap: set MTU on the remote Pascal Mazon
2017-03-14 8:34 ` [dpdk-dev] [PATCH v4] net/tap: remote netdevice traffic capture Pascal Mazon
2017-03-14 8:34 ` [dpdk-dev] [PATCH v4] net/tap: add " Pascal Mazon
2017-03-14 14:00 ` Wiles, Keith
2017-03-15 15:03 ` [dpdk-dev] [PATCH v5] net/tap: " Pascal Mazon
2017-03-15 15:03 ` [dpdk-dev] [PATCH v5] net/tap: add " Pascal Mazon
2017-03-23 8:42 ` [dpdk-dev] [PATCH v6 0/1] net/tap: " Pascal Mazon
2017-03-23 8:42 ` [dpdk-dev] [PATCH v6 1/1] net/tap: add " Pascal Mazon
2017-03-24 15:48 ` 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=33A6CFE9-FE2E-444F-9333-309D32EE70FD@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=pascal.mazon@6wind.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).