DPDK patches and discussions
 help / color / mirror / Atom feed
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 v4] net/tap: add remote netdevice traffic capture
Date: Tue, 14 Mar 2017 14:00:54 +0000	[thread overview]
Message-ID: <7F8C927D-2B15-4DBE-9F62-F2AB2BA7B432@intel.com> (raw)
In-Reply-To: <fb20954d367b9d2d855bab6fbf45b7098ff3360a.1489480278.git.pascal.mazon@6wind.com>


> On Mar 14, 2017, at 4:34 PM, Pascal Mazon <pascal.mazon@6wind.com> wrote:
> 
> By default, a tap netdevice is of no use when not fed by a separate
> process. The ability to automatically feed it from another netdevice
> allows applications to capture any kind of traffic normally destined to
> the kernel stack.
> 
> This patch implements this ability through a new optional "remote"
> parameter.
> 
> Packets matching filtering rules created with the flow API are matched
> on the remote device and redirected to the tap PMD, where the relevant
> action will be performed.
> 
> Signed-off-by: Pascal Mazon <pascal.mazon@6wind.com>
> Acked-by: Olga Shern <olgas@mellanox.com>

Acked-by: Keith Wiles <keith.wiles@intel.com>

> ---
> doc/guides/nics/tap.rst       |  17 ++
> drivers/net/tap/rte_eth_tap.c | 101 +++++++++-
> drivers/net/tap/rte_eth_tap.h |   4 +
> drivers/net/tap/tap_flow.c    | 451 ++++++++++++++++++++++++++++++++++++++++--
> drivers/net/tap/tap_flow.h    |  24 +++
> 5 files changed, 575 insertions(+), 22 deletions(-)

Regards,
Keith

  reply	other threads:[~2017-03-14 14:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 12:27 [dpdk-dev] [PATCH 0/4] net/tap: " 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 ` [dpdk-dev] [PATCH 0/4] net/tap: remote netdevice traffic capture Wiles, Keith
2017-03-07 16:38 ` [dpdk-dev] [PATCH v2 0/4] " 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 [this message]
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=7F8C927D-2B15-4DBE-9F62-F2AB2BA7B432@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).