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, 3 Jan 2019 14:28:34 -0800 From: Jakub Kicinski <jakub.kicinski@...ronome.com> To: Eran Ben Elisha <eranbe@...lanox.com> Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "David S. Miller" <davem@...emloft.net>, Jiri Pirko <jiri@...lanox.com>, Moshe Shemesh <moshe@...lanox.com>, Aya Levin <ayal@...lanox.com>, Tal Alon <talal@...lanox.com>, Ariel Almog <ariela@...lanox.com> Subject: Re: [PATCH RFC net-next 00/19] Devlink health reporting and recovery system On Thu, 3 Jan 2019 13:31:59 +0000, Eran Ben Elisha wrote: > Arch wise those are two different features which we shouldn't mix. > The region dump is aiming at dumping of information for monitoring of > "HW memory" at real time, more like a dumb channel to provide memory > chunks from HW to user. The "real time read" part of the region dump was not even implemented. And it was the part that made most sense to me. Region snapshots were described as a tool for gathering crash dumps. See bedc989b0c98 ("net/mlx4_core: Add Crdump FW snapshot support"). The "chunks from HW" is also incorrect as (1) current implementation of regions seem to mostly revolve around FW state and (2) there is nothing in the man page etc. that says HW. I'm not saying region snapshots fit the bill perfectly for you, I'm saying you guys are adding a second facility to do a very similar thing in the span of 6 months - how is it unreasonable of me to ask to consolidate? But I'm not gonna fight you any more on this, if nobody else cares.
Powered by blists - more mailing lists