DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: "Gal Cohen (Product)" <galco@mellanox.com>,
	Flavio Leitner <fbl@redhat.com>,
	Ian Stokes <ian.stokes@intel.com>
Subject: Re: [dpdk-dev] DPDK 20.08 Mellanox Roadmap
Date: Wed, 24 Jun 2020 18:55:28 +0200	[thread overview]
Message-ID: <4048657.SOpcSorSZm@thomas> (raw)
In-Reply-To: <AM6PR05MB50785AEFFC4F3F4132752A1EC3B30@AM6PR05MB5078.eurprd05.prod.outlook.com>

+Cc Ian & Flavio who discussed flow mirroring in OvS meeting.
See below what Mellanox is submitting:

25/05/2020 15:30, Gal Cohen (Product):
> [2] Support flow-based traffic sampling or mirroring:
> Packets of a given classification, can be cloned at a given sampling rate and forwarded to a vport or queue. When the sampling rate is set to 100% the traffic would be completely mirrored.
> Once sampled or mirrored, a packet may be bound to an additional action such as mark, encap, decap.
> Motivation: Enable monitoring and statistics on classified traffic for business or lawful interception.
> Example: Monitoring of hairpined traffic;

      reply	other threads:[~2020-06-24 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 13:30 Gal Cohen (Product)
2020-06-24 16:55 ` Thomas Monjalon [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4048657.SOpcSorSZm@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=fbl@redhat.com \
    --cc=galco@mellanox.com \
    --cc=ian.stokes@intel.com \


* 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).