[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221117193618.2cd47268@kernel.org>
Date: Thu, 17 Nov 2022 19:36:18 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Leon Romanovsky <leon@...nel.org>
Cc: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>,
"Samudrala, Sridhar" <sridhar.samudrala@...el.com>,
netdev@...r.kernel.org, davem@...emloft.net, pabeni@...hat.com,
edumazet@...gle.com, intel-wired-lan@...ts.osuosl.org,
jiri@...dia.com, anthony.l.nguyen@...el.com,
alexandr.lobakin@...el.com, wojciech.drewek@...el.com,
lukasz.czapnik@...el.com, shiraz.saleem@...el.com,
jesse.brandeburg@...el.com, mustafa.ismail@...el.com,
przemyslaw.kitszel@...el.com, piotr.raczynski@...el.com,
jacob.e.keller@...el.com, david.m.ertman@...el.com,
leszek.kaliszczuk@...el.com, Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: [PATCH net-next 00/13] resource management using devlink reload
On Thu, 17 Nov 2022 19:38:48 +0200 Leon Romanovsky wrote:
> I don't think that management of PCI specific parameters in devlink is
> right idea. PCI has his own subsystem with rules and assumptions, netdev
> shouldn't mangle them.
Not netdev, devlink, which covers netdev, RDMA and others.
> In MSI-X case, this even more troublesome as users
> sees these values through lspci without driver attached to it.
I'm no PCI expert either but FWIW to me the patch set seems reasonable.
Whether management FW policies are configured via core PCI sysfs or
subsystem-specific-ish APIs is a toss up. Adding Bjorn and please CC him
on the next rev.
Link to the series:
https://lore.kernel.org/all/20221114125755.13659-1-michal.swiatkowski@linux.intel.com/
Powered by blists - more mailing lists