lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 8 Oct 2020 09:39:05 +0200 From: Jiri Pirko <jiri@...nulli.us> To: Moshe Shemesh <moshe@...lanox.com> Cc: "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Jiri Pirko <jiri@...dia.com>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH net-next v2 03/16] devlink: Add devlink reload limit option Wed, Oct 07, 2020 at 08:00:44AM CEST, moshe@...lanox.com wrote: >Add reload limit to demand restrictions on reload actions. >Reload limits supported: >no_reset: No reset allowed, no down time allowed, no link flap and no > configuration is lost. > >By default reload limit is unspecified and so no constraints on reload >actions are required. > >Some combinations of action and limit are invalid. For example, driver >can not reinitialize its entities without any downtime. > >The no_reset reload limit will have usecase in this patchset to >implement restricted fw_activate on mlx5. > >Have the uapi parameter of reload limit ready for future support of >multiselection. > >Signed-off-by: Moshe Shemesh <moshe@...lanox.com> Reviewed-by: Jiri Pirko <jiri@...dia.com>
Powered by blists - more mailing lists