From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <users-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 1E6FBA0546
	for <public@inbox.dpdk.org>; Wed, 26 May 2021 09:10:32 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id A9FBF40150;
	Wed, 26 May 2021 09:10:31 +0200 (CEST)
Received: from mail.deltatec.be (mail.deltatec.be [91.183.90.4])
 by mails.dpdk.org (Postfix) with ESMTP id A5D1E4003F
 for <users@dpdk.org>; Wed, 26 May 2021 09:10:30 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=deltacast.tv;
 s=AnsUTM; 
 h=MIME-Version:Content-Type:Message-ID:Date:Subject:To:From;
 bh=Qki3nCldRbuHftWPWi/j6RCkwau0+VvrOoDrIY/Ko5o=; 
 b=Y73ehY4M3CUM8wg1agTtV559zViw8Je1wZbBnPzI1CBaAaVWCmbwKr4+bfjVbDUqNhXNkz9DHAiFE52D4q3EoET//zo9esknDjRl/YaEf7iwQl5cjPNuTnoX3DGxgNnNH7Y4SG1zxDxeAexuG+lBwGVVlSfdMv19bByV6ohhT7M=;
Received: from [172.16.4.5] (port=24382 helo=W2K19-SVR-5.office.deltatec.net)
 by mail.deltatec.be with esmtp (Exim 4.82_1-5b7a7c0-XX)
 (envelope-from <a.pollenus@deltacast.tv>) id 1llngN-0006lK-1j
 for users@dpdk.org; Wed, 26 May 2021 09:10:23 +0200
Received: from W2K16-SVR-20.office.deltatec.net (172.16.4.20) by
 W2K19-SVR-5.office.deltatec.net (172.16.4.5) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.2.792.3; 
 Wed, 26 May 2021 09:10:23 +0200
Received: from W2K16-SVR-20.office.deltatec.net ([::1]) by
 W2K16-SVR-20.office.deltatec.net ([::1]) with mapi id 15.01.2176.002; Wed, 26
 May 2021 09:10:23 +0200
X-CTCH-RefID: str=0001.0A782F22.60ADF45F.00C9, ss=1, re=0.000, recu=0.000,
 reip=0.000, cl=1, cld=1, fgs=0
From: Antoine POLLENUS <a.pollenus@deltacast.tv>
To: "users@dpdk.org" <users@dpdk.org>
Thread-Topic: Re: [dpdk-users] Issues with rte_flow_destroy
Thread-Index: AddR/am54l/+KTNwQAOkBNFLNFmFaQ==
Date: Wed, 26 May 2021 07:10:23 +0000
Message-ID: <0f358466baa147f79e7d6c983df630ba@deltacast.tv>
Accept-Language: en-US, fr-BE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.6.165]
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
Subject: Re: [dpdk-users] Issues with rte_flow_destroy
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
Errors-To: users-bounces@dpdk.org
Sender: "users" <users-bounces@dpdk.org>

I've also test using directly the flow director capabilities using ethtool =
and there it seems there is no issues I can make the same work flow as I wa=
nt.

I've also test through DPDK with a XL710 (40G) and I have the same issues i=
t seems the issue come from someware in the i40e functions. Maybe the valid=
ate.

This is really blocking for us and I have no idea how to fix that or any wo=
rk around.

thank you in advance for your help,

regards

Antoine Pollenus