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

Message-Id: <1260006955.3565.12.camel@localhost>
Date:	Sat, 05 Dec 2009 01:55:55 -0800
From:	Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RFC: how to control device specific features.  sysfs or mod param?

This is a general question to folks to get some kind of consensus on
controlling device-specific modes.  Currently in ixgbe, I can have two
different modes of our Flow Director mechanism.  One is the current one
in use today, the other is part of a patchset for programming n-tuple
filters that will be submitted soon.

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?

Thanks,
-PJ Waskiewicz

--
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