From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D48B6C433DF for ; Wed, 5 Aug 2020 09:27:04 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 3453D20792 for ; Wed, 5 Aug 2020 09:27:04 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3453D20792 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9C4831BFF5; Wed, 5 Aug 2020 11:27:03 +0200 (CEST) Received: from huawei.com (szxga04-in.huawei.com [45.249.212.190]) by dpdk.org (Postfix) with ESMTP id 61F3537B4 for ; Wed, 5 Aug 2020 11:27:01 +0200 (CEST) Received: from DGGEMS401-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id A30F19CD644D5910F60D; Wed, 5 Aug 2020 17:26:50 +0800 (CST) Received: from localhost.localdomain (10.69.192.56) by DGGEMS401-HUB.china.huawei.com (10.3.19.201) with Microsoft SMTP Server id 14.3.487.0; Wed, 5 Aug 2020 17:26:41 +0800 From: Chengchang Tang To: CC: , , , , Date: Wed, 5 Aug 2020 17:24:44 +0800 Message-ID: <1596619484-19714-1-git-send-email-tangchengchang@huawei.com> X-Mailer: git-send-email 2.7.4 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.69.192.56] X-CFilter-Loop: Reflected Subject: [dpdk-dev] [PATCH] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 --- 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..f931091 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 named rx_buf_size will be added to the public data + structure ``rte_eth_rxq_info`` to indicate the buffer size used in receiving + pkts 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 planed 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