All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Mazon <pascal.mazon@6wind.com>
To: keith.wiles@intel.com
Cc: dev@dpdk.org, Pascal Mazon <pascal.mazon@6wind.com>
Subject: [PATCH v5] net/tap: remote netdevice traffic capture
Date: Wed, 15 Mar 2017 16:03:39 +0100	[thread overview]
Message-ID: <cover.1489590192.git.pascal.mazon@6wind.com> (raw)
In-Reply-To: <cover.1488967463.git.pascal.mazon@6wind.com>

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

v2 changes:
  - rebase on top of updated "net/tap: support flow API"
  - fix implicit flow flush when closing the netdevices

v3 changes:
  - memset(0) for remote_iface in rte_pmd_tap_probe()
  - use snprintf instead of strncpy to correctly handle terminating \0

v4 changes:
  - rebase on top of updated "net/tap: support flow API"
  - use only a single patch now as MTU, MAC and flags can be easily managed
    with tap_ioctl()

v5 changes:
  - rebase after adrien's patches on Tx poll and Rx signaling

Pascal Mazon (1):
  net/tap: add remote netdevice traffic capture

 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(-)

-- 
2.8.0.rc0

  parent reply	other threads:[~2017-03-15 15:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 12:27 [PATCH 0/4] net/tap: remote netdevice traffic capture Pascal Mazon
2017-03-03 12:27 ` [PATCH 1/4] net/tap: add " Pascal Mazon
2017-03-03 12:27 ` [PATCH 2/4] net/tap: reflect tap flags on the remote Pascal Mazon
2017-03-03 12:27 ` [PATCH 3/4] net/tap: use the remote MAC address if available Pascal Mazon
2017-03-03 12:27 ` [PATCH 4/4] net/tap: set MTU on the remote Pascal Mazon
2017-03-03 15:54 ` [PATCH 0/4] net/tap: remote netdevice traffic capture Wiles, Keith
2017-03-07 16:38 ` [PATCH v2 0/4] " Pascal Mazon
2017-03-07 16:38   ` [PATCH v2 1/4] net/tap: add " Pascal Mazon
2017-03-07 16:38   ` [PATCH v2 2/4] net/tap: reflect tap flags on the remote Pascal Mazon
2017-03-07 16:38   ` [PATCH v2 3/4] net/tap: use the remote MAC address if available Pascal Mazon
2017-03-07 16:38   ` [PATCH v2 4/4] net/tap: set MTU on the remote Pascal Mazon
2017-03-08 10:06   ` [PATCH v3 0/4] net/tap: remote netdevice traffic capture Pascal Mazon
2017-03-08 10:06     ` [PATCH v3 1/4] net/tap: add " Pascal Mazon
2017-03-08 10:06     ` [PATCH v3 2/4] net/tap: reflect tap flags on the remote Pascal Mazon
2017-03-08 10:06     ` [PATCH v3 3/4] net/tap: use the remote MAC address if available Pascal Mazon
2017-03-08 10:06     ` [PATCH v3 4/4] net/tap: set MTU on the remote Pascal Mazon
2017-03-14  8:34     ` [PATCH v4] net/tap: remote netdevice traffic capture Pascal Mazon
2017-03-14  8:34       ` [PATCH v4] net/tap: add " Pascal Mazon
2017-03-14 14:00         ` Wiles, Keith
2017-03-15 15:03     ` Pascal Mazon [this message]
2017-03-15 15:03       ` [PATCH v5] " Pascal Mazon
2017-03-23  8:42       ` [PATCH v6 0/1] net/tap: " Pascal Mazon
2017-03-23  8:42         ` [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=cover.1489590192.git.pascal.mazon@6wind.com \
    --to=pascal.mazon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.