From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752390AbbFBWby (ORCPT ); Tue, 2 Jun 2015 18:31:54 -0400 Received: from mail-qc0-f174.google.com ([209.85.216.174]:35882 "EHLO mail-qc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751948AbbFBWbg (ORCPT ); Tue, 2 Jun 2015 18:31:36 -0400 Message-ID: <556E2EC2.3020104@cumulusnetworks.com> Date: Tue, 02 Jun 2015 15:31:30 -0700 From: nolan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Scott Feldman , Guenter Roeck CC: Vivien Didelot , Netdev , "David S. Miller" , Florian Fainelli , Andrew Lunn , Jiri Pirko , Jerome Oufella , "linux-kernel@vger.kernel.org" , kernel@savoirfairelinux.com, Chris Healy Subject: Re: [RFC 3/9] net: dsa: mv88e6xxx: add support for VTU ops References: <1433208470-25338-1-git-send-email-vivien.didelot@savoirfairelinux.com> <1433208470-25338-4-git-send-email-vivien.didelot@savoirfairelinux.com> <556D522E.90607@roeck-us.net> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/02/2015 12:44 AM, Scott Feldman wrote: > 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. Scott, I'm confused by this. I think you're saying this config is problematic: br0: eth0.100, eth1.100 br1: eth2.100, eth3.100 But this works fine today. Could you clarify the issue you're referring to? Thanks, - nolan