[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2795f30c-2816-651b-e2bf-c7c08deb6352@nvidia.com>
Date: Tue, 15 Sep 2020 22:59:42 +0300
From: Moshe Shemesh <moshe@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>,
Moshe Shemesh <moshe@...lanox.com>
CC: "David S. Miller" <davem@...emloft.net>,
Jiri Pirko <jiri@...lanox.com>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next RFC v4 15/15] devlink: Add
Documentation/networking/devlink/devlink-reload.rst
On 9/15/2020 7:04 PM, Jakub Kicinski wrote:
> External email: Use caution opening links or attachments
>
>
> On Mon, 14 Sep 2020 09:08:02 +0300 Moshe Shemesh wrote:
>> + * - ``no_reset``
>> + - No reset allowed, no down time allowed, no link flap and no
>> + configuration is lost.
> It still takes the PCI link down for up to 2sec. So there is down time,
> right?
No, the fw reset with PCI link down is categorized as fw_activate with
limit level none.
fw_live_patch keeps the pci link up and it fits to "no_reset" limit level.
Powered by blists - more mailing lists