From: John Fastabend <john.r.fastabend@intel.com>
To: shemminger@vyatta.com, mst@redhat.com, davem@davemloft.net,
bhutchings@solarflare.com, sri@us.ibm.com
Cc: hadi@cyberus.ca, jeffrey.t.kirsher@intel.com,
netdev@vger.kernel.org, gregory.v.rose@intel.com,
krkumar2@in.ibm.com
Subject: [net-next PATCH v2 0/8] Managing the forwarding database(FDB)
Date: Wed, 11 Apr 2012 23:57:07 -0700 [thread overview]
Message-ID: <20120412064858.3112.65818.stgit@jf-dev1-dcblab> (raw)
The following series is a submission for net-next to allow
embedded switches and other stacked devices other then the
Linux bridge to manage a forwarding database.
Previously posted and discussed here,
http://lists.openwall.net/netdev/2012/03/19/26
This version addresses feedback from Ben Hutchings to fix
a typo in the multicast dump routines and to better handle
error cases on add/del fdb. Notify hooks were added for
the NTF_SELF case as well to bring it inline with the
SW net/bridge.
Additionally this version changes the macvlan patch to use
a flag to disable promisc mode. This was decided on over
adding additional modes.
Thanks for the feedback and review. I've tested this with
the 'br' tool published by Stephen Hemminger and pktgen.
.John
---
Greg Rose (1):
ixgbe: UTA table incorrectly programmed
John Fastabend (7):
macvlan: add FDB bridge ops and macvlan flags
ixgbe: allow RAR table to be updated in promisc mode
ixgbe: enable FDB netdevice ops
net: rtnetlink notify events for FDB NTF_SELF adds and deletes
net: add fdb generic dump routine
net: addr_list: add exclusive dev_uc_add and dev_mc_add
net: add generic PF_BRIDGE:RTM_ FDB hooks
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 121 ++++++++---
drivers/net/macvlan.c | 61 +++++-
include/linux/if_link.h | 3
include/linux/if_macvlan.h | 1
include/linux/neighbour.h | 3
include/linux/netdevice.h | 25 ++
include/linux/rtnetlink.h | 4
net/bridge/br_device.c | 3
net/bridge/br_fdb.c | 128 +++---------
net/bridge/br_netlink.c | 12 -
net/bridge/br_private.h | 15 +
net/core/dev_addr_lists.c | 97 ++++++++-
net/core/rtnetlink.c | 267 +++++++++++++++++++++++++
13 files changed, 567 insertions(+), 173 deletions(-)
--
Signature
next reply other threads:[~2012-04-12 7:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 6:57 John Fastabend [this message]
2012-04-12 6:57 ` [net-next PATCH v2 1/8] net: add generic PF_BRIDGE:RTM_ FDB hooks John Fastabend
2012-04-12 6:57 ` [net-next PATCH v2 2/8] net: addr_list: add exclusive dev_uc_add and dev_mc_add John Fastabend
2012-04-12 6:57 ` [net-next PATCH v2 3/8] net: add fdb generic dump routine John Fastabend
2012-04-12 6:57 ` [net-next PATCH v2 4/8] net: rtnetlink notify events for FDB NTF_SELF adds and deletes John Fastabend
2012-04-12 6:57 ` [net-next PATCH v2 5/8] ixgbe: enable FDB netdevice ops John Fastabend
2012-04-12 6:57 ` [net-next PATCH v2 6/8] ixgbe: allow RAR table to be updated in promisc mode John Fastabend
2012-04-12 6:57 ` [net-next PATCH v2 7/8] ixgbe: UTA table incorrectly programmed John Fastabend
2012-04-12 6:57 ` [net-next PATCH v2 8/8] macvlan: add FDB bridge ops and macvlan flags John Fastabend
2012-04-12 8:09 ` John Fastabend
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=20120412064858.3112.65818.stgit@jf-dev1-dcblab \
--to=john.r.fastabend@intel.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=gregory.v.rose@intel.com \
--cc=hadi@cyberus.ca \
--cc=jeffrey.t.kirsher@intel.com \
--cc=krkumar2@in.ibm.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=sri@us.ibm.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.