lkml.org 
[lkml]   [2015]   [Jun]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [RFC 3/9] net: dsa: mv88e6xxx: add support for VTU ops
    On Mon, Jun 1, 2015 at 11:50 PM, Guenter Roeck <linux@roeck-us.net> wrote:

    [cut]

    > I brought this up before. No idea if my e-mail got lost or what happened.
    >
    > We use a fid per port, and a fid per bridge group. With VLANs, this is
    > completely
    > ignored, ahd there is only a single fid per vlan for the entire switch.
    >
    > Either per-port fids are unnecessary as well, or something is wrong here,
    > or I am missing something. Can you explain why we only need a single fid
    > per vlan, even if we have multiple bridge groups and the same vlan is
    > configured in all of them ?

    That brings up an interesting point about having multiple bridges with
    the same vlan configured. I struggled with that problem with rocker
    also and I don't have an answer other than "don't do that". Or,
    better put, if you have multiple bridge on the same vlan, just use one
    bridge for that vlan. Otherwise, I don't know how at the device level
    to partition the vlan between the bridges. Maybe that's what Vivien
    is facing also? I can see how this works for software-only bridges,
    because they should be isolated from each other and independent. But
    when offloading to a device which sees VLAN XXX global across the
    entire switch, I don't see how we can preserve the bridge boundaries.

    I hope I'm not misunderstanding the issue here; if I am, I apologize.

    -scott


    \
     
     \ /
      Last update: 2015-06-02 10:21    [W:2.129 / U:0.192 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site