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 34C60A0547; Mon, 27 Sep 2021 08:19:27 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0CB0F40686; Mon, 27 Sep 2021 08:19:27 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 63E6F4003D for ; Mon, 27 Sep 2021 08:19:25 +0200 (CEST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D18645C010E; Mon, 27 Sep 2021 02:19:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 27 Sep 2021 02:19:24 -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=fm2; bh= I5AfQe6Ix2uHc3nK+Lq8stR6Ek2KKBb2Qrok5N4tTSM=; b=RqPrMxnNcc+wdv02 8Mn1D3wEgN9evc4Wqzrsg3G97DRorVSSXmeYSQ1B22IoJVbtjRAVd6Nsf6k5mpJI rUxzK3nvgJUH4LV1VwbYKIknm6N6acVasdWkZc9ZSGklSibkoaPTS6SPRowSLeUA TdjnBdUu4/+Wb3oMQuIAOYlQ7e9+pB4yC58VMhFK8CAKmQipBh1XcaAYm2Phe8le r9FjYN4a+PPZfp8wsY3W5XHIybUJSClKgo1HEQ5IZYy9M7sgzl9xhMn3dWe90cM1 Yp4sFp5V4Xj4j9iFKz2mUtAaKKLO5UB/B71gO7dnKdzOy4sJCxKQc8JpnAxxL1yW yZCcUw== 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=fm3; bh=I5AfQe6Ix2uHc3nK+Lq8stR6Ek2KKBb2Qrok5N4tT SM=; b=T5a6fQtgTp0GGV0HzaNRcgUCjo+dx1BYTO5YTyCFOrbHbDu77mkvjSh1d OyBlqK8a9DRbJXMr9Dmy9L+mSkBy0jYSt1/loma9WxCXH/JeQ4cpV4syOHNsNcRh zdFN6NPXmHB9o73HSvRo6ULxWiOSX59/0QdmNJcFgDXfUL+/Ls9I4Km5HPCc/BHz ojahG6ut7xQ3T8iLL7S1zVWY+o1om+vYJJ0yY4dcKXGU8al0BMu90W0CiMCa7/gf SrTggRs53fShqWCoQpQwTT7UoWHtl7LBtubwcflsZYO3TkZcTIrCIw1ox4JE35DA 3tIKdf58he1G2kUT/brfFy2K6xU7Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudejjedguddthecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdej ueeiiedvffegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 27 Sep 2021 02:19:23 -0400 (EDT) From: Thomas Monjalon To: Jie Wang Cc: dev@dpdk.org, ferruh.yigit@intel.com, andrew.rybchenko@oktetlabs.ru, xiaoyun.li@intel.com, stevex.yang@intel.com Date: Mon, 27 Sep 2021 08:19:21 +0200 Message-ID: <2103588.zk1eQJicq0@thomas> In-Reply-To: <20210926092055.495322-2-jie1x.wang@intel.com> References: <20210827081740.365037-1-jie1x.wang@intel.com> <20210926092055.495322-1-jie1x.wang@intel.com> <20210926092055.495322-2-jie1x.wang@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v9 1/3] ethdev: add an API to get device configuration info 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" 26/09/2021 11:20, Jie Wang: > This patch adds a new API "rte_eth_dev_conf_info_get()" to help users get > device configuration info. > > Cc: stable@dpdk.org No we don't backport new features. > Signed-off-by: Jie Wang [...] > + * Retrieve the configuration of an Ethernet device. > + * > + * @param port_id > + * The port identifier of the Ethernet device. > + * @param dev_conf_info > + * A pointer to a structure of type *rte_eth_conf* to be filled with > + * the configuration of the Ethernet device. > + * And the memory of the structure should be allocated by the caller. > + * @return > + * - (0) if successful. > + * - (-ENODEV) if *port_id* invalid. > + * - (-EINVAL) if bad parameter. > + */ > +__rte_experimental > +int rte_eth_dev_conf_info_get(uint16_t port_id, > + struct rte_eth_conf *dev_conf_info); It does not make sense to me. rte_eth_conf is passed by the app to rte_eth_dev_configure. Why the app would need to get the same info back?