On Tue, 17 Jan 2006 23:16:43 +0100 Stefan Rompf <[EMAIL PROTECTED]> wrote:
> Am Dienstag 17 Januar 2006 20:42 schrieb Jouni Malinen: > > > Sure, you can do it that way, too. However, this is not the only use. I > > just remembered another one: QoS. Devicescape 802.11 code uses a qdisc > > on the master interface to take care of determining which hardware TX > > queue to use with WMM (which uses four different TX queues). > > so after all, it should be an implementation detail whether our master device > is a struct net_device or not, depending on how much infrastructure of the > networking core we need at this point. > > Stefan What ever it is, it needs to be a kobject, to allow for sysfs to work. Also, please make it hot removable (like netdevices) so module can be unloaded at any time (independent of ref counts). Look at bonding, bridging, and VLAN to see how layered devices can work. -- Stephen Hemminger <[EMAIL PROTECTED]> OSDL http://developer.osdl.org/~shemminger - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
