netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, Florian Fainelli <f.fainelli@gmail.com>,
	vivien.didelot@savoirfairelinux.com,
	jerome.oufella@savoirfairelinux.com, linux@roeck-us.net,
	andrew@lunn.ch, cphealy@gmail.com
Subject: [PATCH net-next v3 0/3] net: dsa: integration with SWITCHDEV for HW bridging
Date: Tue, 24 Feb 2015 13:15:31 -0800	[thread overview]
Message-ID: <1424812534-8936-1-git-send-email-f.fainelli@gmail.com> (raw)

Hi all,

This patch set provides the DSA and SWITCHDEV integration bits together and
modifies the bcm_sf2 driver accordingly such that it works properly with HW
bridging.

Changes in v3:

- add back the null pointer check in dsa_slave_br_port_mask from Guenter
- slightly rework patch 1 commit message not to mention the function name
  we add in patch 2

Changes in v2:

- avoid a race condition in how DSA network devices are created, patch from
  Guenter Roeck
- provide a consistent and work STP state once a port leaves the bridge
- retain a bridge device pointer to properly flag port/bridge membership
- properly flush the ARL (Address Resolution Logic) in bcm_sf2.c
- properly retain port membership when individually bringing devices up/down
  while they are members of a bridge

We discussed on the mailing-list the possibility of standardizing a "fdb_flush"
operation for DSA switch drivers, looking at the Marvell and Broadcom switches,
I am not convinced this is practical or diserable as the terminologies vary
here, but there is nothing preventing us from doing it later.

Many thanks to Guenter and Andrew for both testing and providing feedback.

Thanks!

Florian Fainelli (2):
  net: dsa: integrate with SWITCHDEV for HW bridging
  net: dsa: bcm_sf2: add HW bridging support

Guenter Roeck (1):
  net: dsa: Ensure that port array elements are initialized before being
    used

 drivers/net/dsa/bcm_sf2.c      | 155 ++++++++++++++++++++++++++++++++++++++-
 drivers/net/dsa/bcm_sf2.h      |   2 +
 drivers/net/dsa/bcm_sf2_regs.h |  15 ++++
 include/net/dsa.h              |  10 +++
 net/dsa/Kconfig                |   1 +
 net/dsa/dsa.c                  |  17 +++--
 net/dsa/dsa_priv.h             |   9 ++-
 net/dsa/slave.c                | 161 +++++++++++++++++++++++++++++++++++++++--
 8 files changed, 352 insertions(+), 18 deletions(-)

-- 
2.1.0

             reply	other threads:[~2015-02-24 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 21:15 Florian Fainelli [this message]
2015-02-24 21:15 ` [PATCH net-next v3 1/3] net: dsa: Ensure that port array elements are initialized before being used Florian Fainelli
2015-02-24 21:15 ` [PATCH net-next v3 2/3] net: dsa: integrate with SWITCHDEV for HW bridging Florian Fainelli
2015-02-25  5:44   ` Guenter Roeck
2015-02-24 21:15 ` [PATCH net-next v3 3/3] net: dsa: bcm_sf2: add HW bridging support Florian Fainelli
2015-02-25 22:04 ` [PATCH net-next v3 0/3] net: dsa: integration with SWITCHDEV for HW bridging 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=1424812534-8936-1-git-send-email-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=cphealy@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jerome.oufella@savoirfairelinux.com \
    --cc=linux@roeck-us.net \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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 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).