From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f176.google.com (mail-wr0-f176.google.com [209.85.128.176]) by dpdk.org (Postfix) with ESMTP id E7E71D28A for ; Wed, 29 Mar 2017 11:45:31 +0200 (CEST) Received: by mail-wr0-f176.google.com with SMTP id l43so7027339wre.1 for ; Wed, 29 Mar 2017 02:45:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=TRAm5T5Tn2GyFqWkhQxC5xGTVZ2nSdcdP1F/KQS1QL8=; b=ClNmYs44yvFqB6SrxcBC8Kj5fPWLch6OIJb6xZpoGArXMTvTNj4+0AL/uTkXbdW3g3 PoUlbVoy/ME64ozGrOrBAYT553h4MxWirEUzypLUXNbe7QsX8+1ZMCibJy0Tt510lWIV xxsq6LCw7O6XZk3CCbHmeSQtE8Tv1NP/YsGSB9axdCgsGN0QMmUlcZn713mGkwMqUGBn 9WEtuWS/33XeFgw+iI1mPeeUXs7zgVL3YZTVfiOzMfTRWWWYFk3dKZVgTshbyRVn7wni cEmq6HgvAxGhidzwqvhVp137dTHMJVPzs/jFIjZRvRyBguCsYMs02v0fcz/ftY2nwmgb BITw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=TRAm5T5Tn2GyFqWkhQxC5xGTVZ2nSdcdP1F/KQS1QL8=; b=LtVeexGLuNsPV3lx+TNnsmab5q0dARATpGXsbZsEQp8JA1mksbi0ht3bwStm4AZpPZ WQ/kVPMg/CcrnwdtXWA0LEYslEgu8gvLGl1W5EGKCMcaC+JZfzfzsQh0CG8DW3zeXKYu SumCecdrZY7PUUqcf0qaK3hMsXzI/NB251JrdvFCUZzRFvc8liIz11HEkzHfX4A5+lZE KjUBSByQ/QkECBMs7ipML9bcomYkI/j/Q0UGJIX5EH/jVCulUXKR84jTaVtcgRjrMpn1 z3o/EjvwiI4b8MG6LA2KRsENcQdiYdWrOZXcAjTPI7fMPT6xphKnCbtCFGVxJMMDLdzR NMHg== X-Gm-Message-State: AFeK/H2saFN01QsMSOpAG0BPHsbvDwQWIm4ETdDgiRtcI/mwuolMdcd1lJFm/wD+HSTjZzu3 X-Received: by 10.28.69.147 with SMTP id l19mr451708wmi.55.1490780731583; Wed, 29 Mar 2017 02:45:31 -0700 (PDT) Received: from autoinstall.dev.6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id g78sm8679417wrd.11.2017.03.29.02.45.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 02:45:31 -0700 (PDT) Date: Wed, 29 Mar 2017 11:45:23 +0200 From: =?iso-8859-1?Q?N=E9lio?= Laranjeiro To: "Legacy, Allain" Cc: "Adrien Mazarguil (adrien.mazarguil@6wind.com)" , "dev@dpdk.org" , "Peters, Matt" Message-ID: <20170329094523.GG16796@autoinstall.dev.6wind.com> References: <70A7408C6E1BFB41B192A929744D8523968F8E2F@ALA-MBC.corp.ad.wrs.com> <20170328153602.GC16796@autoinstall.dev.6wind.com> <70A7408C6E1BFB41B192A929744D8523968F92EF@ALA-MBC.corp.ad.wrs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <70A7408C6E1BFB41B192A929744D8523968F92EF@ALA-MBC.corp.ad.wrs.com> User-Agent: Mutt/1.5.23 (2014-03-12) 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: Wed, 29 Mar 2017 09:45:32 -0000 I Allain, Please see below On Tue, Mar 28, 2017 at 04:16:08PM +0000, Legacy, Allain wrote: > > -----Original Message----- > > From: Nélio Laranjeiro [mailto:nelio.laranjeiro@6wind.com] > > Sent: Tuesday, March 28, 2017 11:36 AM > <..> > > If I understand correctly, your application is adding 500 rules like: > > > > flow create 0 ingress pattern eth src is dst is / vlan vid is > > / end action mark id is / queue index 0 / end > > > > Almost... the only difference is that the ETH pattern also checks for type=0x8100 Ethernet type was not supported in DPDK 17.02, it was submitted later in march [1]. Did you embed the patch in your test? > > > Once the flows are setup, the application then checks that ingress > > > packets are properly marked with the intended unique integer specified > > > in the MARK action. > > > > It is sending packets to verify this? > > The traffic generator continues to send packets during the test. > Once all flow rules have been created the application expects further > ingress packets will be marked with the unique ID. > > > > When I run this test after the NIC has been reset there are no issues. > > > > What do you mean by "reset"? > > The DPDK test application is quit and restarted therefore the NIC is > re-probed, configured, started, etc. Seems like this is cleaning up > whatever problem is resident in the NIC that is causing the new flow > rules to not work properly. > > > > In mlx5 PMD rte_flow_destroy() always returns success as the destruction > > should never fail. > > Can you compile in debug mode (by setting > > CONFIG_RTE_LIBRTE_MLX5_DEBUG to "y")? Then you should have as many > > print for the creation rules than the destroyed ones. > > I can give that a try. Thanks, [1] http://dpdk.org/ml/archives/dev/2017-March/058722.html -- Nélio Laranjeiro 6WIND