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 0/5] net: support binding vlan dev link state to vlan member bridge ports
Date: Fri, 19 Apr 2019 15:01:59 +0300	[thread overview]
Message-ID: <e5048157-a9da-3921-2e7c-3e6f248735a2@cumulusnetworks.com> (raw)
In-Reply-To: <20190418173535.22925-1-mmanning@vyatta.att-mail.com>

On 18/04/2019 20:35, Mike Manning wrote:
> For vlan filtering on bridges, the bridge may also have vlan devices
> as upper devices. For switches, these are used to provide L3 packet
> processing for ports that are members of a given vlan.
> 
> While it is correct that the admin state for these vlan devices is
> either set directly for the device or inherited from the lower device,
> the link state is also transferred from the lower device. So this is
> always up if the bridge is in admin up state and there is at least one
> bridge port that is up, regardless of the vlan that the port is in.
> 
> The link state of the vlan device may need to track only the state of
> the subset of ports that are also members of the corresponding vlan,
> rather than that of all ports.
> 
> This series provides an optional vlan flag so that the link state of
> the vlan device is only up if there is at least one bridge port that is
> up AND is a member of the corresponding vlan.
> 
> v2:
>    - Address review comments from Nikolay Aleksandrov
>      in patches 3 & 4 and add patch 5 to address bridge link down due to STP
> v3:
>    - Address review comment from Nikolay Aleksandrov
>      in patch 4 so as to remove unnecessary inline #ifdef
> 
> Mike Manning (5):
>   vlan: support binding link state to vlan member bridge ports
>   vlan: do not transfer link state in vlan bridge binding mode
>   bridge: support binding vlan dev link state to vlan member bridge
>     ports
>   bridge: update vlan dev state when port added to or deleted from vlan
>   bridge: update vlan dev link state for bridge netdev changes
> 
>  include/uapi/linux/if_vlan.h |   9 +-
>  net/8021q/vlan.c             |  18 +++-
>  net/8021q/vlan_dev.c         |  22 +++--
>  net/8021q/vlan_netlink.c     |   3 +-
>  net/bridge/br.c              |  13 ++-
>  net/bridge/br_private.h      |  14 +++
>  net/bridge/br_vlan.c         | 214 +++++++++++++++++++++++++++++++++++++++++++
>  7 files changed, 272 insertions(+), 21 deletions(-)
> 

Hi Mike,
Thanks for doing all the changes, the set looks good. One tip for future reference
when someone is reviewing a set and sends their ack/review/signed-off please keep
it in the respective patches unless they have changed or need to be reviewed again.

Cheers,
 Nik



  parent reply	other threads:[~2019-04-19 18:27 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
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 ` Nikolay Aleksandrov [this message]
2019-04-19 20:58 ` [PATCH net-next v3 0/5] net: support binding vlan dev link state to vlan member bridge ports 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=e5048157-a9da-3921-2e7c-3e6f248735a2@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.