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.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 31F70C433B4 for ; Thu, 15 Apr 2021 00:39:46 +0000 (UTC) Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by mail.kernel.org (Postfix) with ESMTP id 8EFF761220 for ; Thu, 15 Apr 2021 00:39:45 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8EFF761220 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 93B92161DB5; Thu, 15 Apr 2021 02:39:43 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by mails.dpdk.org (Postfix) with ESMTP id C1DBC161D2E for ; Thu, 15 Apr 2021 02:39:41 +0200 (CEST) IronPort-SDR: 5omvq6azxuutVC9W7zb+bufU2AS7+27DlFSVGIMByBkmPP60yT+58cqfhQeF7TIevAbyCCwufz i/4lCv6sHVnQ== X-IronPort-AV: E=McAfee;i="6200,9189,9954"; a="280080476" X-IronPort-AV: E=Sophos;i="5.82,223,1613462400"; d="scan'208";a="280080476" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Apr 2021 17:39:36 -0700 IronPort-SDR: qAZ8Cn0954oIeJSbLUrPfcv2T1/nURC+fFwmwjkjt7ShV+ks62MR8HZUFwroT3NXNIVr146Lb+ H1ZxsXaqvB0A== X-IronPort-AV: E=Sophos;i="5.82,223,1613462400"; d="scan'208";a="461424679" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.204.163]) ([10.213.204.163]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Apr 2021 17:39:35 -0700 To: "Min Hu (Connor)" , dev@dpdk.org References: <1618321639-57642-1-git-send-email-humin29@huawei.com> <1618321639-57642-7-git-send-email-humin29@huawei.com> From: Ferruh Yigit X-User: ferruhy Message-ID: Date: Thu, 15 Apr 2021 01:39:29 +0100 MIME-Version: 1.0 In-Reply-To: <1618321639-57642-7-git-send-email-humin29@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH 6/9] net/hns3: report the speed capability for PF 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" On 4/13/2021 2:47 PM, Min Hu (Connor) wrote: > From: Huisong Li > > The speed capability of the device can be reported to the upper-layer app > in rte_eth_dev_info_get API. In this API, the speed capability is derived > from the 'supported_speed', which is the speed capability actually > supported by the NIC. The value of the 'supported_speed' is obtained > once in the probe stage and may be updated in the scheduled task to deal > with the change of the transmission interface. > > Signed-off-by: Huisong Li > Signed-off-by: Min Hu (Connor) <...> > @@ -2688,6 +2749,7 @@ hns3_dev_infos_get(struct rte_eth_dev *eth_dev, struct rte_eth_dev_info *info) > .nb_mtu_seg_max = hw->max_non_tso_bd_num, > }; > > + info->speed_capa = hns3_get_speed_capa(hw); Can you please update 'hns3.ini', to advertise 'Speed capabilities' support?