From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by dpdk.org (Postfix) with ESMTP id 7E8582A5E for ; Thu, 30 Mar 2017 18:53:55 +0200 (CEST) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.15.2/8.15.1) with ESMTPS id v2UGrq6T011929 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Mar 2017 09:53:52 -0700 (PDT) Received: from ALA-MBC.corp.ad.wrs.com ([fe80::fcbe:9b7:1141:89a1]) by ALA-HCA.corp.ad.wrs.com ([147.11.189.40]) with mapi id 14.03.0294.000; Thu, 30 Mar 2017 09:53:51 -0700 From: "Legacy, Allain" To: =?iso-8859-1?Q?N=E9lio_Laranjeiro?= CC: "Adrien Mazarguil (adrien.mazarguil@6wind.com)" , "dev@dpdk.org" , "Peters, Matt" Thread-Topic: mlx5 flow create/destroy behaviour Thread-Index: AdKnMyKcTaS3607RSaKQ40k6XSEFIQA4IsgAAA2cfDAAGG8RgAAJYfVAAC/SdQAABrqVoA== Date: Thu, 30 Mar 2017 16:53:47 +0000 Message-ID: <70A7408C6E1BFB41B192A929744D8523968FCD16@ALA-MBC.corp.ad.wrs.com> References: <70A7408C6E1BFB41B192A929744D8523968F8E2F@ALA-MBC.corp.ad.wrs.com> <20170328153602.GC16796@autoinstall.dev.6wind.com> <70A7408C6E1BFB41B192A929744D8523968F92EF@ALA-MBC.corp.ad.wrs.com> <20170329094523.GG16796@autoinstall.dev.6wind.com> <70A7408C6E1BFB41B192A929744D8523968F9CBF@ALA-MBC.corp.ad.wrs.com> <20170330130320.GR16796@autoinstall.dev.6wind.com> In-Reply-To: <20170330130320.GR16796@autoinstall.dev.6wind.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.224.140.166] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] mlx5 flow create/destroy behaviour X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 16:53:56 -0000 > -----Original Message----- > From: N=E9lio Laranjeiro [mailto:nelio.laranjeiro@6wind.com] > Sent: Thursday, March 30, 2017 9:03 AM <...>=20 > I found an issue on the id retrieval while receiving an high rate of the > same flow [1]. You may face the same issue. Can you verify with the > patch? >=20 > Thanks, >=20 > [1] http://dpdk.org/dev/patchwork/patch/22897/ I had some difficulty applying that patch onto v17.02 so I took all of the = patches to the mlx5 driver that are in dpdk-next-net just to be sure I had = all other outstanding fixes.=20 The behavior did not change. I still see flows that are not marked even af= ter a flow rule has been created to match on that particular flow. It se= ems like it works in batches... 10-20 flows will work, and then the next 10= -20 flows won't work, and then the next 10-20 flows will work. But, in al= l cases I have logs that show that the flow rules were created properly for= all flows, and destroyed properly at the end of each test. It seems pre= tty consistent that the first test after a NIC reset always works on all fl= ows, but then subsequent tests see variable results. Every so often I get = another test run that has no issues but then the failure pattern resumes on= the next attemp.=20