[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200601144436.75bab03f@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Mon, 1 Jun 2020 14:44:36 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Michael Chan <michael.chan@...adcom.com>,
Vasundhara Volam <vasundhara-v.volam@...adcom.com>,
David Miller <davem@...emloft.net>,
Netdev <netdev@...r.kernel.org>, Jiri Pirko <jiri@...lanox.com>
Subject: Re: [PATCH v2 net-next 1/4] devlink: Add new "allow_fw_live_reset"
generic device parameter.
On Mon, 1 Jun 2020 08:39:18 +0200 Jiri Pirko wrote:
> > If the permanent (NVRAM) parameter is true, all loaded new drivers
> > will indicate support for this feature and set the runtime value to
> > true by default. The runtime value would not be true if any loaded
> > driver is too old or has set the runtime value to false.
>
> This is a bit odd. It is a configuration, not an indication. When you
> want to indicate what you support something, I think it should be done
> in a different place. I think that "devlink dev info" is the place to
> put it, I think that we need "capabilities" there.
Could you explain the need for "capabilities" under dev info?
I don't like catch-all mechanisms in principle. Better if capabilities
are expressed by the API dedicated to configuration of a given feature.
In this particular example the ability to do live reset is clearly
expressed by the presence of the parameter (as implemented by this set).
Powered by blists - more mailing lists