| To: | Ben Greear <greearb@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | 802.1q Was (Re: Plans for 2.5 / 2.6 ??? |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | Wed, 31 May 2000 20:26:28 -0400 (EDT) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <3933777C.E562388C@candelatech.com> |
| Sender: | owner-netdev@xxxxxxxxxxx |
Ben, Your architecture of maintaining a device per VLAN does not scale; (as you might have heard from your numerous attempts to change device lookups). What is the specific reason that you insist on mapping a VLAN to a device? Have you thought of using a VLAN lookup table instead? cheers, jamal I am only asking because i think that sooner than later we need to have 802.1p/q in the kernel and your current scheme is problematic. BTW, it seems there is another 802.1p/q project at sourceforge; |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] eepro100 device name <-> pci bus/slot/func mapping, Anton Blanchard |
|---|---|
| Next by Date: | Re: 802.1q Was (Re: Plans for 2.5 / 2.6 ???, Mitchell Blank Jr |
| Previous by Thread: | Re: Plans for 2.5 / 2.6 ???, Ben Greear |
| Next by Thread: | Re: 802.1q Was (Re: Plans for 2.5 / 2.6 ???, Mitchell Blank Jr |
| Indexes: | [Date] [Thread] [Top] [All Lists] |