All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: roopa@nvidia.com, bridge@lists.linux-foundation.org,
	Nikolay Aleksandrov <nikolay@nvidia.com>
Subject: [PATCH net-next 0/2] net: bridge: multicast: add mdb and host context support
Date: Wed, 21 Jul 2021 17:01:25 +0300	[thread overview]
Message-ID: <20210721140127.773194-1-razor@blackwall.org> (raw)

From: Nikolay Aleksandrov <nikolay@nvidia.com>

Hi,
This is a minor context improvement which chooses the proper multicast
context when adding user mdb entries or host-joined entries (pointing to
the bridge device). Patch 01 adds a helper which chooses the proper
context when user-space is adding an mdb entry, note that it requires
the vlan to be configured on at least 1 device (port or bridge) so it
would have a multicast context. Patch 02 changes br_multicast_host_join
to take a bridge multicast context parameter which is passed down from
the respective functions, currently it is used for the timer config
value only. This set is in preparation for adding all multicast options
for vlans.

Thanks,
 Nik


Nikolay Aleksandrov (2):
  net: bridge: multicast: add mdb context support
  net: bridge: multicast: add context support for host-joined groups

 net/bridge/br_mdb.c       | 45 +++++++++++++++++++++++++++++++++++----
 net/bridge/br_multicast.c |  8 +++----
 net/bridge/br_private.h   |  3 ++-
 3 files changed, 47 insertions(+), 9 deletions(-)

-- 
2.31.1


WARNING: multiple messages have this Message-ID (diff)
From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: bridge@lists.linux-foundation.org,
	Nikolay Aleksandrov <nikolay@nvidia.com>,
	roopa@nvidia.com
Subject: [Bridge] [PATCH net-next 0/2] net: bridge: multicast: add mdb and host context support
Date: Wed, 21 Jul 2021 17:01:25 +0300	[thread overview]
Message-ID: <20210721140127.773194-1-razor@blackwall.org> (raw)

From: Nikolay Aleksandrov <nikolay@nvidia.com>

Hi,
This is a minor context improvement which chooses the proper multicast
context when adding user mdb entries or host-joined entries (pointing to
the bridge device). Patch 01 adds a helper which chooses the proper
context when user-space is adding an mdb entry, note that it requires
the vlan to be configured on at least 1 device (port or bridge) so it
would have a multicast context. Patch 02 changes br_multicast_host_join
to take a bridge multicast context parameter which is passed down from
the respective functions, currently it is used for the timer config
value only. This set is in preparation for adding all multicast options
for vlans.

Thanks,
 Nik


Nikolay Aleksandrov (2):
  net: bridge: multicast: add mdb context support
  net: bridge: multicast: add context support for host-joined groups

 net/bridge/br_mdb.c       | 45 +++++++++++++++++++++++++++++++++++----
 net/bridge/br_multicast.c |  8 +++----
 net/bridge/br_private.h   |  3 ++-
 3 files changed, 47 insertions(+), 9 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-07-21 14:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 14:01 Nikolay Aleksandrov [this message]
2021-07-21 14:01 ` [Bridge] [PATCH net-next 0/2] net: bridge: multicast: add mdb and host context support Nikolay Aleksandrov
2021-07-21 14:01 ` [PATCH net-next 1/2] net: bridge: multicast: add mdb " Nikolay Aleksandrov
2021-07-21 14:01   ` [Bridge] " Nikolay Aleksandrov
2021-07-21 14:01 ` [PATCH net-next 2/2] net: bridge: multicast: add context support for host-joined groups Nikolay Aleksandrov
2021-07-21 14:01   ` [Bridge] " Nikolay Aleksandrov
2021-07-21 21:50 ` [PATCH net-next 0/2] net: bridge: multicast: add mdb and host context support patchwork-bot+netdevbpf
2021-07-21 21:50   ` [Bridge] " patchwork-bot+netdevbpf

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=20210721140127.773194-1-razor@blackwall.org \
    --to=razor@blackwall.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=roopa@nvidia.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.