netdev - Re: [patch net-next 2/3] mlxsw: expose EMAD transactions statistics via debugfs

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150827062704.GE2228@nanopsycho.orion>
Date:	Thu, 27 Aug 2015 08:27:04 +0200
From:	Jiri Pirko <jiri@...nulli.us>
To:	David Miller <davem@...emloft.net>
Cc:	sfeldma@...il.com, netdev@...r.kernel.org, idosch@...lanox.com,
	eladr@...lanox.com, ogerlitz@...lanox.com, jiri@...lanox.com
Subject: Re: [patch net-next 2/3] mlxsw: expose EMAD transactions statistics
 via debugfs

Thu, Aug 27, 2015 at 08:01:15AM CEST, davem@...emloft.net wrote:
>From: Jiri Pirko <jiri@...nulli.us>
>Date: Thu, 27 Aug 2015 07:40:04 +0200
>
>> Switch object itselt would not help you to expose rocker internals. I
>> don't think that you can find generic way, same for all drivers, to
>> expose internal tables and stuff. That is hw specific.
>
>Tables are datastructures with names and types.
>
>Is it not possible to describe datastructures and their types with
>user visible interfaces?

I'm not saying it is not possible, it certainly is. But I think that for
example rocker internals have no value to default user, he should not
care and he cannot find out what is going on there without knowledge or
rocker.c code. The question is, do we need some standard interface to
expose random debugging data? I don't think so, I think that debugfs is
exactly the tool to be used in that case.

>
>Anyone against what I am saying right now is simply lazy.

Not lazy, just thinking :)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html