netdev - Re: RFC: how to control device specific features. sysfs or mod param?

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: <20091205.022540.250826631.davem@davemloft.net>
Date:	Sat, 05 Dec 2009 02:25:40 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	peter.p.waskiewicz.jr@...el.com
Cc:	netdev@...r.kernel.org
Subject: Re: RFC: how to control device specific features. sysfs or mod
 param?

From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>
Date: Sat, 05 Dec 2009 02:22:53 -0800

> Yes, I looked at either ethtool or extending any of the existing
> rtnetlink interfaces.  But my problem with those is this setting is very
> specific to my hardware, and I'm not sure anyone else could benefit from
> this.
> 
> I could try and make it as generic as possible, say pass a 32 or 64-bit
> generic bitfield to a driver through an ethtool operation, and each
> driver would apply some secret sauce based on the bitfield?

We support device specific statistics in a nice way in ethtool, why
don't we do something similar for device specific settings?

A variable length array of names (strings) and values.

This is pretty straightforward for what %99.9999 of uses will be,
boolean enables.  If we make the value type a u32 we can handle pretty
much all the other cases as well.
--
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