[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150827054004.GA2228@nanopsycho.orion>
Date: Thu, 27 Aug 2015 07:40:04 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Scott Feldman <sfeldma@...il.com>
Cc: David Miller <davem@...emloft.net>,
Netdev <netdev@...r.kernel.org>,
Ido Schimmel <idosch@...lanox.com>, eladr@...lanox.com,
"ogerlitz@...lanox.com" <ogerlitz@...lanox.com>,
Jiri Pirko <jiri@...lanox.com>
Subject: Re: [patch net-next 2/3] mlxsw: expose EMAD transactions statistics
via debugfs
Wed, Aug 26, 2015 at 08:21:59PM CEST, sfeldma@...il.com wrote:
>On Wed, Aug 26, 2015 at 10:49 AM, David Miller <davem@...emloft.net> wrote:
>> From: Jiri Pirko <jiri@...nulli.us>
>> Date: Wed, 26 Aug 2015 09:37:57 +0200
>>
>>> I don't think that are much more cases like this. Therefore I think that
>>> for this cases, debugfs might be a good way to expose debugging stats.
>>
>> Scott wanted to do similar things in rocker. DSA guys too.
>>
>> Every switch device is going to have some kind of hierarchy like
>> this, it's not a unique situation.
>
>We've been able to get buy so far without a user-visible device for
>the switch. The switch ports are represented by netdevs, so that's
>easy. How can we create an object for the switch itself, so we can
>attach common interfaces for the user to dump switch-level stats or
>tables? Using another netdev doesn't seem right. Do we need a new
>device class for switches, and then create some common tool/interfaces
>for switch device class?
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.
--
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
Powered by blists - more mailing lists