netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
Cc: netdev@vger.kernel.org, Taras Chornyi <tchornyi@marvell.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	linux-kernel@vger.kernel.org (open list),
	lkp@intel.com, Yevhen Orlov <yevhen.orlov@plvision.eu>
Subject: Re: [PATCH V3 net-next 4/4] net: marvell: prestera: implement software MDB entries allocation
Date: Thu, 30 Jun 2022 20:23:17 -0700	[thread overview]
Message-ID: <20220630202317.0605dbd2@kernel.org> (raw)
In-Reply-To: <20220630111822.26004-5-oleksandr.mazur@plvision.eu>

On Thu, 30 Jun 2022 14:18:22 +0300 Oleksandr Mazur wrote:
> Define bridge MDB entry (software entry):
>   - entry that get's created upon receiving MDB management events
>     (create/delete), that inherently defines a software entry,
>     which can be enabled (offloaded to the HW) or disabled (removed
>     from HW).
>     This separation is done to achieve a better highlevel
>     management of HW resources - software MDB entry could exist,
>     while it's not necessarily should be configured on the HW.
>     For example: by default, the Linux behavior would not replicate
>     multicast traffic to multicast group members if there's no
>     active multicast router and thus - no actual multicast traffic
>     can be received/sent. So, until multicast router appears on the
>     system no HW configuration should be applied, although SW MDB entries
>     should be tracked.
>     Another example would be altering state of 'multicast enabled' on
>     the bridge: MC_DISABLED should invoke disabling / clearing multicast
>     groups of specified bridge on the HW, yet upon receiving 'multicast
>     enabled' event, driver should reconfigure any existing software MDB
>     groups on the HW.
>     Keeping track of software MDB entries in such way makes it possible
>     to properly react on such events.
> Define bridge MDB port entry (software entry):
>   - entry that helps keeping track (on software - driver - level) of which
>     bridge mebemer interface joined any give MDB group;
> 
> Co-developed-by: Yevhen Orlov <yevhen.orlov@plvision.eu>
> Signed-off-by: Yevhen Orlov <yevhen.orlov@plvision.eu>
> Signed-off-by: Oleksandr Mazur <oleksandr.mazur@plvision.eu>

clang says no:

drivers/net/ethernet/marvell/prestera/prestera_switchdev.c:1017:11: warning: variable 'err' is uninitialized when used here [-Wuninitialized]
                        return err;
                               ^~~
drivers/net/ethernet/marvell/prestera/prestera_switchdev.c:1012:9: note: initialize the variable 'err' to silence this warning
        int err;
               ^
                = 0

      reply	other threads:[~2022-07-01  3:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 11:18 [PATCH V3 net-next 0/4] net: marvell: prestera: add MDB offloading support Oleksandr Mazur
2022-06-30 11:18 ` [PATCH V3 net-next 1/4] net: marvell: prestera: rework bridge flags setting Oleksandr Mazur
2022-06-30 11:18 ` [PATCH V3 net-next 2/4] net: marvell: prestera: define MDB/flood domain entries and HW API to offload them to the HW Oleksandr Mazur
2022-06-30 11:18 ` [PATCH V3 net-next 3/4] net: marvell: prestera: define and implement MDB / flood domain API for entries creation and deletion Oleksandr Mazur
2022-06-30 11:18 ` [PATCH V3 net-next 4/4] net: marvell: prestera: implement software MDB entries allocation Oleksandr Mazur
2022-07-01  3:23   ` Jakub Kicinski [this message]

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=20220630202317.0605dbd2@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=oleksandr.mazur@plvision.eu \
    --cc=pabeni@redhat.com \
    --cc=tchornyi@marvell.com \
    --cc=yevhen.orlov@plvision.eu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).