From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 62E35A052B; Thu, 6 Aug 2020 06:03:00 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0E9CF1C044; Thu, 6 Aug 2020 06:02:55 +0200 (CEST) Received: from huawei.com (szxga05-in.huawei.com [45.249.212.191]) by dpdk.org (Postfix) with ESMTP id 748382BF1 for <dev@dpdk.org>; Thu, 6 Aug 2020 06:02:52 +0200 (CEST) Received: from DGGEMS406-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id 55C00275AF257BADE622; Thu, 6 Aug 2020 12:02:50 +0800 (CST) Received: from localhost.localdomain (10.69.192.56) by DGGEMS406-HUB.china.huawei.com (10.3.19.206) with Microsoft SMTP Server id 14.3.487.0; Thu, 6 Aug 2020 12:02:43 +0800 From: Chengchang Tang <tangchengchang@huawei.com> To: <dev@dpdk.org> CC: <linuxarm@huawei.com>, <thomas@monjalon.net>, <ferruh.yigit@intel.com>, <arybchenko@solarflare.com>, <stephen@networkplumber.org> Date: Thu, 6 Aug 2020 12:00:45 +0800 Message-ID: <1596686446-8138-1-git-send-email-tangchengchang@huawei.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1596619484-19714-1-git-send-email-tangchengchang@huawei.com> References: <1596619484-19714-1-git-send-email-tangchengchang@huawei.com> MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.69.192.56] X-CFilter-Loop: Reflected Subject: [dpdk-dev] [PATCH v2] doc: add new field to rxq info struct X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> Struct rte_eth_rxq_info will be modified to include a new field, indicating the size of each buffer that could be used for hw to receive packets. Add this field to rte_eth_rxq_info to expose relevant information to upper layer users/application. For more details: https://mails.dpdk.org/archives/dev/2020-July/176135.html Signed-off-by: Chengchang Tang <tangchengchang@huawei.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com> --- v2: - Remove field name. - Fix some spelling mistakes. --- doc/guides/rel_notes/deprecation.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index ea4cfa7..f08b5f9 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -110,6 +110,15 @@ Deprecation Notices break the ABI checks, that is why change is planned for 20.11. The list of internal APIs are mainly ones listed in ``rte_ethdev_driver.h``. +* ethdev: A new field will be added to the public data structure + ``rte_eth_rxq_info`` to indicate the buffer size used in receiving packets + for HW. When receive packets, HW DMA won't exceed this size. And it will + affect the number of fragments in receiving packets when scatter is enabled. + So, add this field to ``rte_eth_rxq_info`` to expose relevant information to + upper layer user/application. + This change is planned for 20.11. For more details: + https://mails.dpdk.org/archives/dev/2020-July/176135.html + * traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly made ABI stable in the v19.11 release. The TM maintainer and other contributors have agreed to keep the TM APIs as experimental in expectation of additional spec -- 2.7.4