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 04362A0C51; Wed, 21 Jul 2021 17:56:09 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DE38140696; Wed, 21 Jul 2021 17:56:09 +0200 (CEST) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mails.dpdk.org (Postfix) with ESMTP id 6F8694014D for ; Wed, 21 Jul 2021 17:56:08 +0200 (CEST) Received: from dpdk-test7.liberouter.org ([IPv6:2001:718:800:ff00:2eea:7fff:fef8:8792]) (authenticated bits=0) by eva.fit.vutbr.cz (8.16.1/8.16.1) with ESMTPSA id 16LFtxsD081871 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 21 Jul 2021 17:56:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stud.fit.vutbr.cz; s=studfit; t=1626882964; bh=i2R2jLpZvXsBZwtl3bB8XGTswYQRgw4aHP4G9UdTH80=; h=From:To:Cc:Subject:Date; b=pZYFOv5nbT+zd2RroCy+1WnX3T3f49HWwRG0kiQvBe/JZ6OPbfEhwd3A3+AGPFEB5 dDv5bSx9R1pe7dp/0btahqQ/CGLULHKEaD+1vcXB1zlQrA8ryAUyfJ2rxRPNpknjhw LS0JWENHjtvYLEATcDKKMxAaKsXxaNBvtoi64mpc= From: Martin Havlik To: xhavli56@stud.fit.vutbr.cz, Matan Azrad , Shahaf Shuler , Viacheslav Ovsiienko , Thomas Monjalon , Asaf Penso , Jiawei Wang , Bing Zhao , Xueming Li , Tal Shnaiderman , Shun Hao , Ciara Power , Bruce Richardson , Michael Baum , Raslan Darawsheh Cc: dev@dpdk.org, Jan Viktorin Date: Wed, 21 Jul 2021 17:55:47 +0200 Message-Id: <20210721155550.188663-2-xhavli56@stud.fit.vutbr.cz> X-Mailer: git-send-email 2.27.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH 1/4] doc: clarify RTE flow behaviour on port stop/start X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" It is now clearly stated that RTE flow rules can be created only after the port is started. Signed-off-by: Martin Havlik --- doc/guides/nics/mlx5.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index f5b727c1ee..119d537adf 100644 --- a/doc/guides/nics/mlx5.rst +++ b/doc/guides/nics/mlx5.rst @@ -1790,21 +1790,25 @@ Notes for rte_flow ------------------ Flows are not cached in the driver. When stopping a device port, all the flows created on this port from the application will be flushed automatically in the background. After stopping the device port, all flows on this port become invalid and not represented in the system. All references to these flows held by the application should be discarded directly but neither destroyed nor flushed. -The application should re-create the flows as required after the port restart. +The application should re-create the flows as required after the port is +started again. + +Creating flows before port start is not permitted. All flows the application +wants to create have to be created after the port is started. Notes for testpmd ----------------- Compared to librte_net_mlx4 that implements a single RSS configuration per port, librte_net_mlx5 supports per-protocol RSS configuration. Since ``testpmd`` defaults to IP RSS mode and there is currently no command-line parameter to enable additional protocols (UDP and TCP as well as IP), the following commands must be entered from its CLI to get the same -- 2.27.0