All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: nikolay@cumulusnetworks.com, netdev@vger.kernel.org,
	roopa@cumulusnetworks.com, bridge@lists.linux-foundation.org,
	vivien.didelot@gmail.com, idosch@mellanox.com, jiri@mellanox.com,
	davem@davemloft.net
Subject: Re: [Bridge] [PATCH net-next] Documentation: networking: Clarify switchdev devices behavior
Date: Thu, 13 Dec 2018 10:26:30 +0100	[thread overview]
Message-ID: <20181213092630.GD1605@lunn.ch> (raw)
In-Reply-To: <20181212230943.757-1-f.fainelli@gmail.com>

> +VLAN filtering
> +~~~~~~~~~~~~~~
> +
> +The Linux bridge allows the configuration of a VLAN filtering mode (compile and
> +run time) which must be observed by the underlying switchdev network
> +device/hardware:
> +
> +- with VLAN filtering turned off: frames ingressing the device with a VID that
> +  is not programmed into the bridge/switch's VLAN table must be forwarded.
> +
> +- with VLAN filtering turned on: frames ingressing the device with a VID that is
> +  not programmed into the bridges/switch's VLAN table must be dropped.

Hi Florian

i forget the details, but there are some difference between VLAN
filtering being disabled at compile time, and disabled at runtime. I
think the expected behaviour is the same, but the switchdev API usage
is slightly different.

> +- when IGMP snooping is turned on, multicast traffic must be selectively flowing
> +  to the appropriate network ports and not flood the entire switch, that must
> +  include the CPU/management port.

224.0.0.X/32 should always be flooded, IGMP is optional for those
groups in the local subnet.

	Andrew

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jiri@mellanox.com,
	idosch@mellanox.com, vivien.didelot@gmail.com,
	nikolay@cumulusnetworks.com, roopa@cumulusnetworks.com,
	bridge@lists.linux-foundation.org, cphealy@gmail.com
Subject: Re: [PATCH net-next] Documentation: networking: Clarify switchdev devices behavior
Date: Thu, 13 Dec 2018 10:26:30 +0100	[thread overview]
Message-ID: <20181213092630.GD1605@lunn.ch> (raw)
In-Reply-To: <20181212230943.757-1-f.fainelli@gmail.com>

> +VLAN filtering
> +~~~~~~~~~~~~~~
> +
> +The Linux bridge allows the configuration of a VLAN filtering mode (compile and
> +run time) which must be observed by the underlying switchdev network
> +device/hardware:
> +
> +- with VLAN filtering turned off: frames ingressing the device with a VID that
> +  is not programmed into the bridge/switch's VLAN table must be forwarded.
> +
> +- with VLAN filtering turned on: frames ingressing the device with a VID that is
> +  not programmed into the bridges/switch's VLAN table must be dropped.

Hi Florian

i forget the details, but there are some difference between VLAN
filtering being disabled at compile time, and disabled at runtime. I
think the expected behaviour is the same, but the switchdev API usage
is slightly different.

> +- when IGMP snooping is turned on, multicast traffic must be selectively flowing
> +  to the appropriate network ports and not flood the entire switch, that must
> +  include the CPU/management port.

224.0.0.X/32 should always be flooded, IGMP is optional for those
groups in the local subnet.

	Andrew

  reply	other threads:[~2018-12-13  9:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 23:09 [Bridge] [PATCH net-next] Documentation: networking: Clarify switchdev devices behavior Florian Fainelli
2018-12-12 23:09 ` Florian Fainelli
2018-12-13  9:26 ` Andrew Lunn [this message]
2018-12-13  9:26   ` Andrew Lunn
2018-12-15 19:35 ` [Bridge] " David Miller
2018-12-15 19:35   ` David Miller
2018-12-16  8:25 ` [Bridge] " Ido Schimmel
2018-12-16  8:25   ` Ido Schimmel
2018-12-16 17:14   ` [Bridge] " Florian Fainelli
2018-12-16 17:14     ` Florian Fainelli
2018-12-18  7:01     ` [Bridge] " Ido Schimmel
2018-12-18  7:01       ` Ido Schimmel
2018-12-18 20:13       ` [Bridge] " Florian Fainelli
2018-12-18 20:13         ` Florian Fainelli
2018-12-22 20:29         ` [Bridge] " Ido Schimmel
2018-12-22 20:29           ` Ido Schimmel
2018-12-17  3:36   ` [Bridge] " Florian Fainelli
2018-12-17  3:36     ` Florian Fainelli
  -- strict thread matches above, loose matches on Subject: below --
2020-07-22 22:52 [Bridge] " Florian Fainelli
2020-07-23  2:25 ` Randy Dunlap
2020-07-23 22:11 ` Vladimir Oltean
2020-07-23 22:58   ` Florian Fainelli
2020-07-24  0:43     ` Vladimir Oltean

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=20181213092630.GD1605@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=idosch@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=roopa@cumulusnetworks.com \
    --cc=vivien.didelot@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.