From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 61347A04C8;
	Fri, 18 Sep 2020 14:56:21 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 0C11F1DA64;
	Fri, 18 Sep 2020 14:56:21 +0200 (CEST)
Received: from office2.cesnet.cz (office2.cesnet.cz [195.113.144.244])
 by dpdk.org (Postfix) with ESMTP id E75361DA63
 for <dev@dpdk.org>; Fri, 18 Sep 2020 14:56:19 +0200 (CEST)
Received: from tanguero.localdomain (okapi.iinfo.cz [213.151.94.184])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest
 SHA256) (No client certificate requested)
 by office2.cesnet.cz (Postfix) with ESMTPSA id 9A839400070
 for <dev@dpdk.org>; Fri, 18 Sep 2020 14:56:19 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz;
 s=office2-2020; t=1600433779;
 bh=gBsJ66lbw6oxN4YDXFU4hRd4LQkspSupdERjBRrA6ck=;
 h=Date:From:To:Subject;
 b=bOkJ9ubyNmGgeNTTpqneVVPiLnGnm2+2IlRWlEKqxWb6tNUZWz/iDlqowjXTIaDdL
 bsBHSnxYweCF6qWC295ib/98rxi8yUm4icqS0Xwz0ztdrYTIhoQM2Iz8pxq2KZvknp
 es8O69cUHC04QaYKVNXWTvGTPbDVJSwGbjgV+kqDQLuMO8fMvc+vABSaknQap8xlTL
 aIFVQ+MYW4Y5tLiz0Y5TcU3mraIDv9l5bXFeBF49Q9Rd7Tq/SClaFPh0kHFxbGZf2n
 JuND6KTaVQvA/KZARzgmhc5vY/K1n0NM2MSKdTUnBIm9mhLSZ7V+uo1+hzTnNs/fP9
 Wgv7Y7b7JoDaw==
Date: Fri, 18 Sep 2020 14:56:18 +0200
From: Jan Viktorin <viktorin@cesnet.cz>
To: dev@dpdk.org
Message-ID: <20200918145618.052ee504@tanguero.localdomain>
Organization: CESNET
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: [dpdk-dev] Duplicating traffic with RTE Flow
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hello all,

we are looking for a way to duplicate ingress traffic in hardware.

There is an example in [1] suggesting to insert two fate actions into
the RTE Flow actions array like:

  flow create 0 ingress pattern end \
      actions queue index 0 / void / queue index 1 / end

But our experience is that PMDs reject two fate actions (tried with
mlx5). Another similar approach would be to deliver every single packet
into two virtual functions:

  flow create 0 ingress pattern end \
     actions vf index 0 / vf index 1 / end 

Third possibility was to use passthru:

  flow create 0 ingress pattern end \
      actions passthru / vf index 0 / end 
  flow create 0 ingress pattern end \
      actions vf index 1 / end 

Again, tried on mlx5 and it does not support the passthru.

Last idea was to use isolate with passthru (to deliver both to DPDK
application and to the kernel) but again there was no support on mlx5
for passthru...

  flow isolate 0 true
  flow create 0 ingress pattern end actions passthru / rss end / end

Is there any other possibility or PMD+NIC that is known to solve such
issue?

Thanks
Jan Viktorin

[1] https://doc.dpdk.org/guides/prog_guide/rte_flow.html#table-rte-flow-redirect-queue-5-3