From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com> To: netdev@vger.kernel.org Cc: roopa@cumulusnetworks.com, davem@davemloft.net, bridge@lists.linux-foundation.org, Nikolay Aleksandrov <nikolay@cumulusnetworks.com> Subject: [PATCH net-next 0/4] net: bridge: add per-vlan state option Date: Thu, 23 Jan 2020 15:28:03 +0200 [thread overview] Message-ID: <20200123132807.613-1-nikolay@cumulusnetworks.com> (raw) Hi, This set adds the first per-vlan option - state, which uses the new vlan infrastructure that was recently added. It gives us forwarding control on per-vlan basis. The first 3 patches prepare the vlan code to support option dumping and modification. We still compress vlan ranges which have equal options, each new option will have to add its own equality check to br_vlan_opts_eq(). The vlans are created in forwarding state by default to be backwards compatible and vlan state is considered only when the port state is forwarding (more info in patch 4). I'll send the selftest for the vlan state with the iproute2 patch-set. Thanks, Nik Nikolay Aleksandrov (4): net: bridge: check port state before br_allowed_egress net: bridge: vlan: add basic option dumping support net: bridge: vlan: add basic option setting support net: bridge: vlan: add per-vlan state include/uapi/linux/if_bridge.h | 2 + net/bridge/Makefile | 2 +- net/bridge/br_device.c | 3 +- net/bridge/br_forward.c | 2 +- net/bridge/br_input.c | 7 +- net/bridge/br_private.h | 58 +++++++++++++- net/bridge/br_vlan.c | 99 ++++++++++++++++++----- net/bridge/br_vlan_options.c | 142 +++++++++++++++++++++++++++++++++ 8 files changed, 287 insertions(+), 28 deletions(-) create mode 100644 net/bridge/br_vlan_options.c -- 2.21.0
WARNING: multiple messages have this Message-ID (diff)
From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com> To: netdev@vger.kernel.org Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>, roopa@cumulusnetworks.com, bridge@lists.linux-foundation.org, davem@davemloft.net Subject: [Bridge] [PATCH net-next 0/4] net: bridge: add per-vlan state option Date: Thu, 23 Jan 2020 15:28:03 +0200 [thread overview] Message-ID: <20200123132807.613-1-nikolay@cumulusnetworks.com> (raw) Hi, This set adds the first per-vlan option - state, which uses the new vlan infrastructure that was recently added. It gives us forwarding control on per-vlan basis. The first 3 patches prepare the vlan code to support option dumping and modification. We still compress vlan ranges which have equal options, each new option will have to add its own equality check to br_vlan_opts_eq(). The vlans are created in forwarding state by default to be backwards compatible and vlan state is considered only when the port state is forwarding (more info in patch 4). I'll send the selftest for the vlan state with the iproute2 patch-set. Thanks, Nik Nikolay Aleksandrov (4): net: bridge: check port state before br_allowed_egress net: bridge: vlan: add basic option dumping support net: bridge: vlan: add basic option setting support net: bridge: vlan: add per-vlan state include/uapi/linux/if_bridge.h | 2 + net/bridge/Makefile | 2 +- net/bridge/br_device.c | 3 +- net/bridge/br_forward.c | 2 +- net/bridge/br_input.c | 7 +- net/bridge/br_private.h | 58 +++++++++++++- net/bridge/br_vlan.c | 99 ++++++++++++++++++----- net/bridge/br_vlan_options.c | 142 +++++++++++++++++++++++++++++++++ 8 files changed, 287 insertions(+), 28 deletions(-) create mode 100644 net/bridge/br_vlan_options.c -- 2.21.0
next reply other threads:[~2020-01-23 13:28 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-23 13:28 Nikolay Aleksandrov [this message] 2020-01-23 13:28 ` [Bridge] [PATCH net-next 0/4] net: bridge: add per-vlan state option Nikolay Aleksandrov 2020-01-23 13:28 ` [PATCH net-next 1/4] net: bridge: check port state before br_allowed_egress Nikolay Aleksandrov 2020-01-23 13:28 ` [Bridge] " Nikolay Aleksandrov 2020-01-23 16:25 ` Stephen Hemminger 2020-01-23 16:25 ` [Bridge] " Stephen Hemminger 2020-01-23 17:58 ` nikolay 2020-01-23 17:58 ` [Bridge] " nikolay 2020-01-23 13:28 ` [PATCH net-next 2/4] net: bridge: vlan: add basic option dumping support Nikolay Aleksandrov 2020-01-23 13:28 ` [Bridge] " Nikolay Aleksandrov 2020-01-23 13:28 ` [PATCH net-next 3/4] net: bridge: vlan: add basic option setting support Nikolay Aleksandrov 2020-01-23 13:28 ` [Bridge] " Nikolay Aleksandrov 2020-01-23 13:28 ` [PATCH net-next 4/4] net: bridge: vlan: add per-vlan state Nikolay Aleksandrov 2020-01-23 13:28 ` [Bridge] " Nikolay Aleksandrov 2020-01-23 21:10 ` [PATCH net-next 0/4] net: bridge: add per-vlan state option Nikolay Aleksandrov 2020-01-23 21:10 ` [Bridge] " Nikolay Aleksandrov
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=20200123132807.613-1-nikolay@cumulusnetworks.com \ --to=nikolay@cumulusnetworks.com \ --cc=bridge@lists.linux-foundation.org \ --cc=davem@davemloft.net \ --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: linkBe 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.