From: "Mintz, Yuval" <yuval.mi...@cavium.com>
Date: Thu, 20 Apr 2017 10:09:28 +0000

>> > Dump some internal state about VFs through debugfs. This provides
>> > information not available with 'ip link show'.
>> 
>> such as?
>> 
>> donnwantobethedebugfspolice, but still, in the 2-3 times we tried to push
>> debugfs to MLNX NIC drivers, Dave disallowed that, and lately the switch
>> team even went further and deleted that portion of the mlxsw driver -- all to
>> all,  I don't see much point for these type of changes, thoughts?
> 
> Don't want to hikjack your thread, but continuing this topic -
> Is there some flat-out disapproval for debugfs in net-next now?
> 
> We're currently internally engaged with adding qed support for register dumps
> [~equivalents for `ethtool -d' outputs] through debugfs, on behalf of storage
> drivers [qedi/qedf] lacking the API for doing that.

I really hate to see debugfs things in networking drivers.  It's a
complete cop out for doing things properly.

I push back, but I can only fight too much.  If people want to keep
adding stupid poorly designed crap endlessly to their drivers there
is only so much I can do...

Reply via email to