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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sun, 17 Feb 2019 10:58:56 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     idosch@...lanox.com
Cc:     netdev@...r.kernel.org, jiri@...lanox.com, andrew@...n.ch,
        mlxsw@...lanox.com, vadimp@...lanox.com
Subject: Re: [PATCH net-next] mlxsw: core: Extend thermal module with per
 QSFP module thermal zones

From: Ido Schimmel <idosch@...lanox.com>
Date: Thu, 14 Feb 2019 20:22:55 +0000

> From: Vadim Pasternak <vadimp@...lanox.com>
> 
> Add a dedicated thermal zone for each QSFP/SFP module. The current
> temperature is obtained from the module's temperature sensor and the
> trip points are set based on the warning and critical thresholds
> read from the module.
> 
> A cooling device (fan) is bound to all the thermal zones. The
> thermal zone governor is set to user space in order to avoid
> collisions between thermal zones.
> For example, one thermal zone might want to increase the speed of
> the fan, whereas another one would like to decrease it.
> 
> Deferring this decision to user space allows the user to the take
> the most suitable decision.
> 
> Signed-off-by: Vadim Pasternak <vadimp@...lanox.com>
> Signed-off-by: Ido Schimmel <idosch@...lanox.com>

Applied, thanks.

Powered by blists - more mailing lists