[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1ca4c809-b696-3f83-54ca-0c635a66e5db@intel.com>
Date: Fri, 10 Jul 2020 13:55:09 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Jiri Pirko <jiri@...nulli.us>,
Vasundhara Volam <vasundhara-v.volam@...adcom.com>,
David Miller <davem@...emloft.net>,
Netdev <netdev@...r.kernel.org>,
Michael Chan <michael.chan@...adcom.com>,
Jiri Pirko <jiri@...lanox.com>,
Michal Kubecek <mkubecek@...e.cz>, moshe@...lanox.com
Subject: Re: [RFC v2 net-next] devlink: Add reset subcommand.
On 7/10/2020 1:39 PM, Jakub Kicinski wrote:
> On Fri, 10 Jul 2020 11:16:51 -0700 Jacob Keller wrote:
>>> We already have notion of "a component" in "devlink dev flash". I think
>>> that the reset component name should be in-sync with the flash.
>>
>> Right. We should re-use the component names from devlink dev info here
>> (just as we do in devlink dev flash).
>
> Let's remember that the SW did not eat the entire world just yet ;)
>
> There are still HW components which don't have FW (and therefore FW
> component to flash) that folks may want to reset.. that's what the
> ethtool reset API was cut to.
>
True enough. I was thinking only in terms of resetting to load new
firmware, which is a different but related problem.
Thanks,
Jake
Powered by blists - more mailing lists