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 0E4F6A0542; Wed, 5 Oct 2022 11:41:37 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E085640A7D; Wed, 5 Oct 2022 11:41:36 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id AEDB140694 for ; Wed, 5 Oct 2022 11:41:35 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 48B505C0139; Wed, 5 Oct 2022 05:41:35 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 05 Oct 2022 05:41:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1664962895; x= 1665049295; bh=uW5aOJMXcpPAZQ8Ed7D2+GOUp6TCCcIr7WMTaqPVhLc=; b=Z Rd/P8maxizqCNqA4yA2ZA8astjiFg38zjaKynig1acLXnnuwbcuP/t2uGM8lKoiE hvzFOfFzeaQ/ibgm6AP9NLjt8s46gD+wsl2XGfUrOcpgRuG3r9JOVeVuPZKolgwj mryNQ8oRsd4EfYp6dtVaUy8bBi6+XpkCOXGXX+1wWCzDrxlboDgB2UlDGsndgUI9 +BD4zGfe/o5wmxXAP/7o+lCzrGCsYhOk97HNEA27CjApFveIbFPMkmpadRXnI6Zl 8ocBjUOo8tvsgqFfvn+yoxZ0Z6XnQFyMYftmQbPPhC9gfDy7sNg/FvdSC1zOoAYr 6aMFLNSyWnwI1hm/qhG/Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1664962895; x= 1665049295; bh=uW5aOJMXcpPAZQ8Ed7D2+GOUp6TCCcIr7WMTaqPVhLc=; b=m Xs1ns6ss7Re4NQSldvbIWWkBfjGkOiKBX1mt3fRsEnTjxraSi65T88BPH0y2rAwz GktsfTtsiD2kkcHXv/5VXr0j6+vHwJ8+sfqd0EfTHUHq1Q6hE6rlWKlopf0Yccyc Vtd4iLmd0dtG23p+iANJmKBfXUBLJoc2jDTPoTDztI/dNU28GRdVgNgLb3LutUVC nQm0Yep18sVzJpmg3jvI5RmTwbopf3ndnRbkjbPsoFMRbZZwNEV0r2PXDAlhYrDa plRkN3RFhii2X68maPoTRGoZ5Yt/zNDPdrGwSli/Cqp9apeYcmjHibVJzW2SQBJs /jHl1kRw8YZUkbASSow9w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeeifedgudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 5 Oct 2022 05:41:32 -0400 (EDT) From: Thomas Monjalon To: Kevin Laatz Cc: David Marchand , dev@dpdk.org, bruce.richardson@intel.com, mb@smartsharesystems.com, lizh@nvidia.com, matan@nvidia.com, stephen@networkplumber.org, lihuisong@huawei.com, Parav Pandit , "Xueming(Steven) Li" , Rosen Xu , Hemant Agrawal , Sachin Saxena , Long Li , Ferruh Yigit Subject: Re: [PATCH v9] eal: add bus cleanup to eal cleanup Date: Wed, 05 Oct 2022 11:41:31 +0200 Message-ID: <18500914.fAMKPKieAE@thomas> In-Reply-To: References: <20220419161438.1837860-1-kevin.laatz@intel.com> <20221004165051.153751-1-kevin.laatz@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 05/10/2022 09:45, David Marchand: > On Tue, Oct 4, 2022 at 6:47 PM Kevin Laatz wrote: > > This patch proposes adding bus cleanup to the eal_cleanup() to make EAL's > > init/exit more symmetrical, ensuring all bus devices are cleaned up > > appropriately without the application needing to be aware of all bus types > > that may have been probed during initialization. > > > > Contained in this patch are the changes required to perform cleanup for > > devices on the PCI bus and VDEV bus during eal_cleanup(). There would be an > > ask for bus maintainers to add the relevant cleanup for their buses since > > they have the domain expertise. > > Cc: maintainers for info. Kevin, When you don't go to the end of a task, you must ask help to complete it. Here you assume others will do it, but you don't even Cc the relevant maintainers. Please could you track that all buses will get the implementation? You should open a bugzilla ticket for each bus, and assign it to the relevant maintainer. Thanks