All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Mike Manning <mmanning@vyatta.att-mail.com>,
	netdev@vger.kernel.org, roopa@cumulusnetworks.com
Subject: Re: [PATCH net-next v3 3/5] bridge: support binding vlan dev link state to vlan member bridge ports
Date: Fri, 19 Apr 2019 14:54:31 +0300	[thread overview]
Message-ID: <8a6a8832-100f-be55-3677-ee5194afcc70@cumulusnetworks.com> (raw)
In-Reply-To: <20190418173535.22925-4-mmanning@vyatta.att-mail.com>

On 18/04/2019 20:35, Mike Manning wrote:
> In the case of vlan filtering on bridges, the bridge may also have the
> corresponding vlan devices as upper devices. A vlan bridge binding mode
> is added to allow the link state of the vlan device to track only the
> state of the subset of bridge ports that are also members of the vlan,
> rather than that of all bridge ports. This mode is set with a vlan flag
> rather than a bridge sysfs so that the 8021q module is aware that it
> should not set the link state for the vlan device.
> 
> If bridge vlan is configured, the bridge device event handling results
> in the link state for an upper device being set, if it is a vlan device
> with the vlan bridge binding mode enabled. This also sets a
> vlan_bridge_binding flag so that subsequent UP/DOWN/CHANGE events for
> the ports in that bridge result in a link state update of the vlan
> device if required.
> 
> The link state of the vlan device is up if there is at least one bridge
> port that is a vlan member that is admin & oper up, otherwise its oper
> state is IF_OPER_LOWERLAYERDOWN.
> 
> Signed-off-by: Mike Manning <mmanning@vyatta.att-mail.com>
> ---
>  net/bridge/br.c         |  13 +++--
>  net/bridge/br_private.h |  14 +++++
>  net/bridge/br_vlan.c    | 151 ++++++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 174 insertions(+), 4 deletions(-)
> 

Acked-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>


  reply	other threads:[~2019-04-19 20:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 17:35 [PATCH net-next v3 0/5] net: support binding vlan dev link state to vlan member bridge ports Mike Manning
2019-04-18 17:35 ` [PATCH net-next v3 1/5] vlan: support binding " Mike Manning
2019-04-19 11:51   ` Nikolay Aleksandrov
2019-04-18 17:35 ` [PATCH net-next v3 2/5] vlan: do not transfer link state in vlan bridge binding mode Mike Manning
2019-04-19 11:51   ` Nikolay Aleksandrov
2019-04-18 17:35 ` [PATCH net-next v3 3/5] bridge: support binding vlan dev link state to vlan member bridge ports Mike Manning
2019-04-19 11:54   ` Nikolay Aleksandrov [this message]
2019-04-18 17:35 ` [PATCH net-next v3 4/5] bridge: update vlan dev state when port added to or deleted from vlan Mike Manning
2019-04-19 11:55   ` Nikolay Aleksandrov
2019-04-18 17:35 ` [PATCH net-next v3 5/5] bridge: update vlan dev link state for bridge netdev changes Mike Manning
2019-04-19 11:59   ` Nikolay Aleksandrov
2019-04-19 12:01 ` [PATCH net-next v3 0/5] net: support binding vlan dev link state to vlan member bridge ports Nikolay Aleksandrov
2019-04-19 20:58 ` David Miller

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=8a6a8832-100f-be55-3677-ee5194afcc70@cumulusnetworks.com \
    --to=nikolay@cumulusnetworks.com \
    --cc=mmanning@vyatta.att-mail.com \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.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.