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 A50BD46091; Wed, 15 Jan 2025 12:36:18 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3A4AE402D6; Wed, 15 Jan 2025 12:36:18 +0100 (CET) Received: from fout-b7-smtp.messagingengine.com (fout-b7-smtp.messagingengine.com [202.12.124.150]) by mails.dpdk.org (Postfix) with ESMTP id BD4354003C for ; Wed, 15 Jan 2025 12:36:16 +0100 (CET) Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfout.stl.internal (Postfix) with ESMTP id 252B711401A2; Wed, 15 Jan 2025 06:36:16 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-09.internal (MEProxy); Wed, 15 Jan 2025 06:36:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1736940975; x=1737027375; bh=ltE8ELdHf0T0EfnlY4VNJjE2y4yLLe2k/aWZHlEnJ90=; b= XQ6z0vnEMwxeVnif03WIjSgjnd3N65/xYVu+mQBtL0bhV4IPsw4nDpzVUaTdU2p0 uFjAfw/EoTQ5zXjsiol8PhCPhkOaDOAXUmBDR5S/fPsH7tt1HpW28oSjL+yvLtha oR9/gtKhCIg19RZTvkNuZg5kdSk9KZY1L/0G6Nj/Ozda1FCF/N+DrNQcvVQN2l8s Qm4HnGsE6PAoucobZWOAbvv6ow2nraVXFZ9taWpMYKhd8LoOcFuCmjN2UC0LcGGr abELTN12st5kxwXHXnpmJ1nMo4QBgH9vSJB9FVI9QiyFoBWGl2PlVP/6sAZWzF47 mBzfHGveyxWxqULmUmNTBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1736940975; x= 1737027375; bh=ltE8ELdHf0T0EfnlY4VNJjE2y4yLLe2k/aWZHlEnJ90=; b=v C70+u7ukNZJ5x6vclp1nXAlmah3534EJIkXUHebIgLLH6yj60OkzgYRGpnvq8DkQ kfmEFX4afqxPAAnwIo35aBKnRSic8pROpG2EboyDEfUetvtFDHRc7zjHfjjHOZHz RHjtCVUAV9EaysKCnH5d12GGGTulTGNAsNH3v43wLynIwhGllCkLDzdongUJZlQj s1hvAskj/ouXVbiIJ5cw0Hg6FQ8p8z7HmDA1NRBYRsaakQbdFuLqObV5PPNh+aPU OPa8yCtGlxCcLSESoMCF4e9DArytbj9clqt2Se9JEdLQG0jXA+4oymdmK/2LZChf aWhoDCu8LgBexwlW9OUtQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrudehledgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhephffvvefufffkjghfggfgtgesthfuredttddtjeen ucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrg hlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpeejudevheeiveduuddtveffgfdtgeek ueevjeffjeegtdeggeekgfdvuefgfeekjeenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtpdhn sggprhgtphhtthhopeehpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopeguvghvse guphgukhdrohhrghdprhgtphhtthhopehlihhhuhhishhonhhgsehhuhgrfigvihdrtgho mhdprhgtphhtthhopehsthgvphhhvghnsehnvghtfihorhhkphhluhhmsggvrhdrohhrgh dprhgtphhtthhopehlihhuhihonhhglhhonhhgsehhuhgrfigvihdrtghomh X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 15 Jan 2025 06:36:14 -0500 (EST) From: Thomas Monjalon To: dev@dpdk.org, Huisong Li Cc: stephen@networkplumber.org, liuyonglong@huawei.com, lihuisong@huawei.com Subject: Re: [PATCH v1 2/2] ethdev: fix some APIs can be used in the new event Date: Wed, 15 Jan 2025 12:36:13 +0100 Message-ID: <1837683.3VsfAaAtOV@thomas> In-Reply-To: <20250115034110.15245-3-lihuisong@huawei.com> References: <20250115034110.15245-1-lihuisong@huawei.com> <20250115034110.15245-3-lihuisong@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 15/01/2025 04:41, Huisong Li: > The rte_eth_dev_socket_id() and rte_eth_dev_owner_*() can be used after > allocating an ethdev. So this patch relaxes the conditions for using them. You should be more explicit: "during probing, before it becomes generally available and considered as valid". Should we add these functions in the comment for RTE_ETH_EVENT_NEW?