From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 38511A0546 for ; Tue, 25 May 2021 14:34:32 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AF65E40150; Tue, 25 May 2021 14:34:31 +0200 (CEST) Received: from mail.deltatec.be (mail.deltatec.be [91.183.90.4]) by mails.dpdk.org (Postfix) with ESMTP id C878A4003F for ; Tue, 25 May 2021 14:34: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=UUGgnWH0bJbiwVFql7VDLO5kbfmyNTWzoPrVrfZyTbc=; b=Fe7t17UxOU7nS7w2Bbe5ZIRbpdmcBXrqiClbGqiOkhrXIOzmrqyK9uAV1PVT1YEwRVZ5PdoYY6Plyb4nSSSZxNB10H5hUBTQnGmjVuVnhzOw9A2rUA/NEygDtgEScXbpjJHoEcOYLv6j+tBkuHSxYt3h9x8Yzr28XjZ+yCgcEIg=; Received: from [172.16.4.5] (port=6592 helo=W2K19-SVR-5.office.deltatec.net) by mail.deltatec.be with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1llWGS-0006Cg-0s for users@dpdk.org; Tue, 25 May 2021 14:34:28 +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; Tue, 25 May 2021 14:34:28 +0200 Received: from W2K16-SVR-20.office.deltatec.net (172.16.4.20) by W2K16-SVR-20.office.deltatec.net (172.16.4.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Tue, 25 May 2021 14:34:27 +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; Tue, 25 May 2021 14:34:27 +0200 X-CTCH-RefID: str=0001.0A782F19.60ACEED4.008F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 From: Antoine POLLENUS To: "users@dpdk.org" Thread-Topic: Issues with rte_flow_destroy Thread-Index: AddRYjKNnSpR1LFNQGmaJomjzlrV+g== Date: Tue, 25 May 2021 12:34:27 +0000 Message-ID: <9cb9a449bf9d48bab080d0e33170c6b6@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: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi, I'm experiencing some issues using the flow API and a intel XXV710 (i40e). I managed to reproduce it in the flow filtering sample. I'm creating one flow than deleting it and then creating another with basic= change #define SRC_IP ((0<<24) + (0<<16) + (0<<8) + 0) /* src ip =3D 0.0.0.0 */ #define SRC_IP_1 ((192<<24) + (168<<16) + (1<<8) + 3) /* dest ip =3D 192.16= 8.1.1 */ #define DEST_IP ((192<<24) + (168<<16) + (1<<8) + 1) /* dest ip =3D 192.168= .1.1 */ #define DEST_IP_1 ((192<<24) + (168<<16) + (1<<8) + 2) /* dest ip =3D 192.1= 68.1.1 */ flow =3D generate_ipv4_flow(port_id, selected_queue, SRC_IP, EMPT= Y_MASK, DEST_IP, FUL= L_MASK, &error); if (!flow) { printf("Flow can't be created %d message: %s= \n", error.type, error.message ? error.messag= e : "(no stated reason)"); rte_exit(EXIT_FAILURE, "error in creating fl= ow"); } //Deleting the rule int returned; returned =3D rte_flow_destroy(port_id, flow, &error); if(returned < 0) { printf("destroy %d message: %s\n", error.type, error.message ? error.messag= e : "(no stated reason)"); } //Generating another rule flow1 =3D generate_ipv4_flow(port_id, selected_queue, SRC_IP_1, FU= LL_MASK, DEST_IP_1, F= ULL_MASK, &error); if (!flow1) { printf("Flow can't be created %d message: %s= \n", error.type, error.message ? error.messag= e : "(no stated reason)"); rte_exit(EXIT_FAILURE, "error in creating fl= ow"); } When doing that I always get an error on the second flow I want to add. Flow can't be created 13 message: Conflict with the first rule's input set. The rule is indeed in conflict because it uses the same as the previous but= with the source IP changing and also the destination IP. The strange thing is that a destroy has been made on the previous rule and = should not be there anymore.... Am I doing something wrong or is there a bug in the destroy function ? Thank you in advance for your answer, Regards, Antoine Pollenus