Tue, Sep 15, 2020 at 10:20:39PM CEST, mo...@nvidia.com wrote:
>
>On 9/15/2020 4:33 PM, Jiri Pirko wrote:
>> Tue, Sep 15, 2020 at 02:30:19PM CEST, mo...@nvidia.com wrote:
>> > On 9/14/2020 4:39 PM, Jiri Pirko wrote:
>> > > Mon, Sep 14, 2020 at 08:07:50AM CEST, mo...@mellanox.com wrote:
>> [..]
>>
>
Tue, Sep 15, 2020 at 02:30:19PM CEST, mo...@nvidia.com wrote:
>
>On 9/14/2020 4:39 PM, Jiri Pirko wrote:
>> Mon, Sep 14, 2020 at 08:07:50AM CEST, mo...@mellanox.com wrote:
[..]
>> > +/**
>> > + *devlink_reload_implicit_actions_performed - Update devlink on
>> > reload actions
>> > + *
On 9/15/2020 4:33 PM, Jiri Pirko wrote:
Tue, Sep 15, 2020 at 02:30:19PM CEST, mo...@nvidia.com wrote:
On 9/14/2020 4:39 PM, Jiri Pirko wrote:
Mon, Sep 14, 2020 at 08:07:50AM CEST, mo...@mellanox.com wrote:
[..]
+/**
+ * devlink_reload_implicit_actions_performed - Update devlink on rel
On 9/14/2020 4:39 PM, Jiri Pirko wrote:
Mon, Sep 14, 2020 at 08:07:50AM CEST, mo...@mellanox.com wrote:
Add reload action stats to hold the history per reload action type and
limit level.
Empty line missing.
Ack.
For example, the number of times fw_activate has been performed on this
dev
Mon, Sep 14, 2020 at 08:07:50AM CEST, mo...@mellanox.com wrote:
>Add reload action stats to hold the history per reload action type and
>limit level.
Empty line missing.
>For example, the number of times fw_activate has been performed on this
>device since the driver module was added or if the f
Add reload action stats to hold the history per reload action type and
limit level.
For example, the number of times fw_activate has been performed on this
device since the driver module was added or if the firmware activation
was performed with or without reset.
Add devlink notification on stats u
