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 30FCFA0C4C; Tue, 5 Oct 2021 19:18:22 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E9CFC413FB; Tue, 5 Oct 2021 19:18:21 +0200 (CEST) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mails.dpdk.org (Postfix) with ESMTP id 382B8413FA for ; Tue, 5 Oct 2021 19:18:20 +0200 (CEST) Received: from dpdk-test7.liberouter.org (rt-tmc-kou.liberouter.org [195.113.172.126]) (authenticated bits=0) by eva.fit.vutbr.cz (8.16.1/8.16.1) with ESMTPSA id 195HGVss048378 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 5 Oct 2021 19:16:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stud.fit.vutbr.cz; s=studfit; t=1633454203; bh=+KwnI2TpBEiFliBlTfsvugo6Yod15oeEd6Y8eOeuAoY=; h=From:To:Cc:Subject:Date; b=HaBjGFl4ieSYuOes2pj1JK9sVtTD9YBGeA1GyLvwtbm5QcysgOmPfZqBli70R9JTW STM0n/fZ7yt7c96VWfIiKCToPGgpFOlXnsasgLxyS0wqugfXS/5PMzun5J4z2bpOMe xvcYWuhn0c0FV7Am3guDb98wQyZzV+R7FC4LJiRQ= From: Martin Havlik To: xhavli56@stud.fit.vutbr.cz Cc: Jan Viktorin , dev@dpdk.org, chas3@att.com, humin29@huawei.com, ferruh.yigit@intel.com, thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru, haiyue.wang@intel.com, ivan.ilchenko@oktetlabs.ru, aman.deep.singh@intel.com, kirankn@juniper.net, lirongqing@baidu.com, ajit.khaparde@broadcom.com Date: Tue, 5 Oct 2021 19:16:11 +0200 Message-Id: <20211005171613.2879-1-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 0/2] net/bonding: fix dedicated queues flow rule issue 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" This patchset stems from [1]. Not all PMDs allow RTE flow rule creation before device start. Introduced capability marks the ones that allow it. The capability is then used to fix flow rule creation for dedicated queues in slave devices in bonding. The introduced capa _will need to be set_ for all appropriate PMDs in `rte_eth_dev_info->dev_capa`. That is not pretty, but it holds the semantics of a capability correctly, as opposed to making it a requirement to have the device started before creating flow rules. [1] https://www.mail-archive.com/dev@dpdk.org/msg214840.html Martin Havlik (2): lib/ethdev: introduce RTE_ETH_DEV_CAPA_FLOW_CREATE_BEFORE_START net/bonding: require started device for dedicated queues drivers/net/bonding/rte_eth_bond_pmd.c | 25 +++++++++++++++++++------ lib/ethdev/rte_ethdev.h | 2 ++ 2 files changed, 21 insertions(+), 6 deletions(-) -- 2.27.0