Netdev List
 help / color / mirror / Atom feed
From: Vivien Didelot <vivien.didelot@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 2/3] net: dsa: mv88e6xxx: add support for bridge flags
Date: Tue, 19 Feb 2019 13:20:08 -0500	[thread overview]
Message-ID: <20190219132008.GB16594@t480s.localdomain> (raw)
In-Reply-To: <a93298cc-7acd-6357-fcee-fe238487c143@gmail.com>

Hi Florian,

On Tue, 19 Feb 2019 09:44:32 -0800, Florian Fainelli <f.fainelli@gmail.com> wrote:
> > OK, thanks for the details. The programming of the broadcast MAC address
> > must be handled in the core then, I will move this from mv88e6xxx up to the
> > DSA layer later, but that's totally orthogonal here.
> 
> I am not sure if it makes sense for us to work hard on supporting
> BR_BCAST_FLOOD, for instance, on Broadcom switches, there does not
> appear to be an easy way to specify whether broadcast traffic will be
> flooded or not, it will be. The only way to tsolve that is to create a
> MDB/FDB entry with negative logic (e.g.: forward to a
> non-existing/connected port). Every other bridge flag typically maps 1:1
> with a corresponding hardware feature, so we should support them.

I think it's best to keep away from driver-specific hacks :-)

Since broadcom floods multicast and BR_BCAST_FLOOD is set by default,
this would simply translate as not implementing a port_flood_bc ops in the
broadcom driver.

But I agree that it doesn't seem necessary to implement support for this yet.


Thanks,

	Vivien

  reply	other threads:[~2019-02-19 18:20 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 14:24 [PATCH net-next 0/3] net: dsa: mv88e6xxx: fix IPv6 Russell King - ARM Linux admin
2019-02-17 14:25 ` [PATCH net-next 1/3] net: dsa: add support for bridge flags Russell King
2019-02-17 21:37   ` Florian Fainelli
2019-02-17 22:04     ` Russell King - ARM Linux admin
2019-02-17 22:07       ` Florian Fainelli
2019-02-18  0:50         ` Russell King - ARM Linux admin
2019-02-18 11:23           ` Russell King - ARM Linux admin
2019-02-19 15:42             ` Vivien Didelot
2019-02-17 14:25 ` [PATCH net-next 2/3] net: dsa: mv88e6xxx: " Russell King
2019-02-17 21:38   ` Florian Fainelli
2019-02-17 14:25 ` [PATCH net-next 3/3] net: dsa: mv88e6xxx: defautl to multicast and unicast flooding Russell King
2019-02-17 14:27   ` Russell King - ARM Linux admin
2019-02-17 16:34     ` Russell King - ARM Linux admin
2019-02-17 21:45       ` Florian Fainelli
2019-02-17 21:58         ` Russell King - ARM Linux admin
2019-02-17 22:03           ` Florian Fainelli
2019-02-17 22:19             ` Russell King - ARM Linux admin
2019-02-17 22:30               ` Florian Fainelli
2019-02-17 16:31 ` [PATCH net-next v2 0/3] net: dsa: mv88e6xxx: fix IPv6 Russell King - ARM Linux admin
2019-02-17 16:32   ` [PATCH net-next v2 1/3] net: dsa: add support for bridge flags Russell King
2019-02-17 16:32   ` [PATCH net-next v2 2/3] net: dsa: mv88e6xxx: " Russell King
2019-02-19 16:16     ` Vivien Didelot
2019-02-19 16:24       ` Russell King - ARM Linux admin
2019-02-19 17:00         ` Vivien Didelot
2019-02-19 17:14           ` Russell King - ARM Linux admin
2019-02-19 17:38             ` Vivien Didelot
2019-02-19 17:44               ` Florian Fainelli
2019-02-19 18:20                 ` Vivien Didelot [this message]
2019-02-19 18:08               ` Russell King - ARM Linux admin
2019-02-19 19:04                 ` Vivien Didelot
2019-02-19 19:10                   ` Russell King - ARM Linux admin
2019-02-19 19:37                     ` Florian Fainelli
2019-02-19 19:56                     ` Vivien Didelot
2019-02-19 22:52                       ` Russell King - ARM Linux admin
2019-02-19 17:00       ` Russell King - ARM Linux admin
2019-02-19 17:23         ` Vivien Didelot
2019-02-19 17:27           ` Russell King - ARM Linux admin
2019-02-19 23:34         ` Russell King - ARM Linux admin
2019-02-19 23:53           ` Florian Fainelli
2019-02-20  0:07             ` Russell King - ARM Linux admin
2019-02-17 16:32   ` [PATCH net-next v2 3/3] net: dsa: mv88e6xxx: default to multicast and unicast flooding Russell King
2019-02-18 12:53     ` Russell King - ARM Linux admin
2019-02-19 16:05       ` Vivien Didelot
2019-02-19 16:18         ` Russell King - ARM Linux admin
2019-02-18 11:34   ` [PATCH net-next v2 0/3] net: dsa: mv88e6xxx: fix IPv6 Russell King - ARM Linux admin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190219132008.GB16594@t480s.localdomain \
    --to=vivien.didelot@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox