From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3C519328243; Thu, 12 Mar 2026 14:36:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773326203; cv=none; b=KbrEYSWK28+//rOJF9NXx/8qlEt3e3v/009ZZceUTrBSOFme2ku6FelFPYDjbsAAhv+QD2kkdZmYFkaDRB6uxw8qVcyfOodsuMcVxDpn/aYbICF86iZNqZz2RdKAhIGaf1fzdr2UKV7XYV1NJn1ikNBYO8CMPfxNZxvMkeof6BU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773326203; c=relaxed/simple; bh=uIol7kReUwc484w6eaVeHC9JSYYQ/xkuA7eqjzZdjWY=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=pDPawfswkXfikqxhzcYO2LxWi1DpWmMp1ztChR6+SWmP5/9KXpp/nhs/cPA/nzB000PaWAEwrLT6kEvf7oXVVL9cRIBafGU8klmwKS2m9fjl4/Nb76/W9JO8UtLGji3MV1Q6o8lS5WEIVV9HCXuD58vA6smkNVsgTxD3xhXvI0I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=fOnWULja; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="fOnWULja" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DFAC3C4CEF7; Thu, 12 Mar 2026 14:36:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1773326202; bh=uIol7kReUwc484w6eaVeHC9JSYYQ/xkuA7eqjzZdjWY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=fOnWULjaWfSeAL+ujb69MF5efDFV+BdDdjL+KJ6LPn1/sq6yWSyEvG19ajrOKCXTB B9C22iW21TAf4Kfv+kkOoWZUbUncIdI6cHV4KkNu1MbG/FKsk0kXSLq4E20/l5bsy8 ltDEl8Zzvs1GWdKYysz6bIX0RXPX4cyvhFPd6xDeB8sCYpyYIt28Ml0ODdbKkxaM6I fmm3xAfvl4FBFjGgoDqXGq4Hp+FOCn0Kq4CeL5iE3cOl3VR5towpDhpuV6pKZpfS6k AX+qozqXUO1sXP2+3opJNOITzdgH1ApO40Xl07WPh9VEzDpIFVqRdWJvKssD5p1e6a baA2jFgDxmXmg== Date: Thu, 12 Mar 2026 07:36:41 -0700 From: Jakub Kicinski To: Jiri Pirko Cc: Or Har-Toov , Tariq Toukan , Eric Dumazet , Paolo Abeni , Andrew Lunn , "David S. Miller" , Donald Hunter , Jonathan Corbet , Saeed Mahameed , Leon Romanovsky , Mark Bloch , Shuah Khan , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-rdma@vger.kernel.org, linux-kselftest@vger.kernel.org, Gal Pressman , Dragos Tatulea , Shay Drory , Jiri Pirko , Moshe Shemesh Subject: Re: [PATCH net-next V3 00/10] devlink: add per-port resource support Message-ID: <20260312073641.027d86e7@kernel.org> In-Reply-To: References: <20260305063729.7e40775d@kernel.org> <20260306120301.0ebe1ab2@kernel.org> <74dcd7c5-8a2b-49a7-a23c-174d17a61955@nvidia.com> <20260309133341.7e08b35d@kernel.org> <5de5103e-e2e4-4b72-9c3c-22847728fbb8@nvidia.com> <20260311145126.7dcca532@kernel.org> <20260312071916.6b759c3f@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Thu, 12 Mar 2026 15:29:53 +0100 Jiri Pirko wrote: > >> I don't see the benefit of exposing the scope to the user to be honest. > >> I mean, dump would show all, dump with "dev" handle would be used as a > >> selector to dump only things related to "dev". What is the use case of > >> this "scope" granularity? > > > >If we follow the logic that dump should show the user relevant > >resources, no matter which sub-object they are attached to - > >having a dev specified should only filter the objects to match > >the dev, including resources which are on ports of that dev. > > > >IDK if there's a strong use case for allowing the user to set > >scope on CLI but also - I don't see why not? > > At least some small sense of consistency with other dumps? Health > reporter and region does not have scope and output mixture of dev-based > and port-based objects. Why to confuse user? That's a judgment call - either we confuse users but two commands behaving differently, or we confuse users with devlink $thing not dumping all instances of the $thing. Especially that drivers often retroactively move $things from device scope to port scope :(