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 8D242A0C44; Fri, 16 Apr 2021 10:58:58 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 195DE141BF3; Fri, 16 Apr 2021 10:58:58 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id 9641D141907 for ; Fri, 16 Apr 2021 10:58:56 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 1BBFD5C00EB; Fri, 16 Apr 2021 04:58:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 16 Apr 2021 04:58:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm1; bh= VCZVKaNO/QqlCm9tGmN3sCmtLbyXXNeQ8tWCIMOx9+Y=; b=ysqlVrewPWuO89ge 7Y6R9GhzxAJ5naoiOwxzQMeS/NYjN8wAJiruxyEUlslglZAqye+TqPRWLe7E0e5n lJKMz4sDQoXsfpFnmv5m/JiksXoWhlGoJPI8It+NOuketBB7GqlwMi/0wSfFrzrL UTc22diD5QC49MZ5AvZJKj99v7lB55c6VXvh0nQoXC5qv5KcJaiCsQo/cs5HVW9Z vNBOnxTy+ZDy0tbu5i52iaouS7oAUUvyvg/V7Oq1qIZ0VCJh6sHDZV1KLe15BgDN sWRKMSLIpe5HZViLn2BUYe0xzqT34ikctUAEBv11SmN+zxzN8uPAfpXwZQGECPuJ gHP2HA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=VCZVKaNO/QqlCm9tGmN3sCmtLbyXXNeQ8tWCIMOx9 +Y=; b=NpKxLLb9e83EWPYsAMlSSaw8ctbBFJV4tjzfhqRsL5K2dSk3BYEQNxww8 WG5KwpyouMFrYZOroiU4w50qviZrrGtLWe+n2Gji+N3/4DkQM1uF9MDyv2NEotmq OaHXLLa4E6Pf/UjF0CH7kJmy8CeeF3u72ffe65ZLV16MTIKQfPYyA6d1N8pU57PZ 13dO7wI8/UxVq+LFJAb4qjv99WGnUpaYWWScZ66CmP90++N3zx5mhpAykBAnVyuX uBHy+xE+ZFbAPL2kk18fXV/c51EnZN4C0TxCJ3BtsFlgRy6FNI2+jlEMoT8kKQgR yM3fYXA+GycXAUxep5ksFI2xFZW2w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudelhedguddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 936891080064; Fri, 16 Apr 2021 04:58:53 -0400 (EDT) From: Thomas Monjalon To: ferruh.yigit@intel.com, Lijun Ou Cc: dev@dpdk.org, linuxarm@openeuler.org, mdr@ashroe.eu Date: Fri, 16 Apr 2021 10:58:51 +0200 Message-ID: <2292057.lhpI95xzKh@thomas> In-Reply-To: <1618562810-20304-1-git-send-email-oulijun@huawei.com> References: <1618454426-21457-1-git-send-email-oulijun@huawei.com> <1618562810-20304-1-git-send-email-oulijun@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH V4] ethdev: add queue state when retrieve queue information 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" 16/04/2021 10:46, Lijun Ou: > Currently, upper-layer application could get queue state only > through pointers such as dev->data->tx_queue_state[queue_id], > this is not the recommended way to access it. So this patch > add get queue state when call rte_eth_rx_queue_info_get and > rte_eth_tx_queue_info_get API. > > Note: After add queue_state field, the 'struct rte_eth_rxq_info' size > remains 128B, and the 'struct rte_eth_txq_info' size remains 64B, so > it could be ABI compatible. [...] > --- a/doc/guides/rel_notes/release_21_05.rst > +++ b/doc/guides/rel_notes/release_21_05.rst > @@ -251,6 +251,12 @@ ABI Changes > function was already marked as internal in the API documentation for it, > and was not for use by external applications. > > +* Added new field ``queue_state`` to ``rte_eth_rxq_info`` structure > + to provide indicated rxq queue state. > + > +* Added new field ``queue_state`` to ``rte_eth_txq_info`` structure > + to provide indicated txq queue state. Not sure we should add a note here for additions which do not break ABI compatibility. It may be confusing.