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.021321.73648278.davem@davemloft.net>
Date:	Sat, 05 Dec 2009 02:13:21 -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 01:55:55 -0800

> My question is I want to toggle the underlying hardware mode to use one
> or the other filter mechanism.  I can either do this using a module
> parameter, which I'd like to avoid, or I can do this in a sysfs
> parameter.  What do people think is the best approach?  Is there another
> option I'm not considering here?

Other than sysfs another option to consider is trying to fit
this into the ethtool framework somehow.
--
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