On 12/11/14 at 09:59am, Varlese, Marco wrote: > An example of attributes are: > * enabling/disabling of learning of source addresses on a given port (you can > imagine the attribute called LEARNING for example); > * internal loopback control (i.e. LOOPBACK) which will control how the flow > of traffic behaves from the switch fabric towards an egress port; > * flooding for broadcast/multicast/unicast type of packets (i.e. BFLOODING, > MFLOODING, UFLOODING);
All of these are highly generic and should *not* be passed through from user space to the driver directly but rather be properly abstracted as Roopa proposed. The value of this API is abstraction. If we introduce per device attributes for generic functions we lose large portions of the value gained. You mentioned you have additional attributes in mind, maybe you can give a few examples which are not generic, i.e. do not apply to multiple vendors. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
