On Tue, 2006-17-01 at 11:42 -0800, Jouni Malinen wrote: > > 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 if i understood correctly: You have a master netdevice which underneath it has child netdevices? > Each > virtual interface do not include own queue and outgoing frames are > queued through the master device (again, this is something that matches > with VLAN implementation). If i understood you correctly, what you are doing is certainly reasonable. Instead of restructuring the netdevice layer to deal with with multiple independent h/ware tx queues you've added a mother device which does intermidiate queueing. > For WMM, the frames in different classes > would need to be scheduled from all virtual interfaces together, not > just separately. Would there be a better way of doing this without using > a master netdev and qdisc/netsched? > I havent been following the thread so i dont understand this problem. Can you explain it in details? cheers, jamal - 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
