From: Jamal Hadi Salim <jhs@mojatatu.com>
To: davem@davemloft.net, stephen@networkplumber.org
Cc: netdev@vger.kernel.org, vyasevic@redhat.com,
sfeldma@cumulusnetworks.com, john.r.fastabend@intel.com,
roopa@cumulusnetworks.com, eric.dumazet@gmail.com
Subject: Re: [net-next PATCH v3 0/2] bridge: more efficient fdb dumping
Date: Wed, 25 Jun 2014 06:25:17 -0400 [thread overview]
Message-ID: <53AAA38D.8090808@mojatatu.com> (raw)
In-Reply-To: <1403691683-14290-1-git-send-email-jhs@emojatatu.com>
I should say I have tested this version against net-next
(the commit message describes the validation tests)
cheers,
jamal
On 06/25/14 06:21, Jamal Hadi Salim wrote:
> From: Jamal Hadi Salim <jhs@mojatatu.com>
>
> Changes:
> V3:
> Suggestion from Eric D. to use for_each_netdev
> Suggestion from Stephen H. to reduce level of indentation
>
> V2:
> Suggestions from Vlad
> Get rid of rcu read lock since rtnl_lock is being held
> simplify for readability
>
>
> Jamal Hadi Salim (2):
> bridge: fdb dumping takes a filter device
> bridge: netlink dump interface at par with brctl
>
> drivers/net/ethernet/intel/i40e/i40e_main.c | 3 +-
> drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c | 5 +-
> include/linux/netdevice.h | 1 +
> include/linux/rtnetlink.h | 1 +
> net/bridge/br_fdb.c | 14 ++++
> net/bridge/br_private.h | 2 +-
> net/core/rtnetlink.c | 77 +++++++++++++++++-----
> 7 files changed, 84 insertions(+), 19 deletions(-)
>
prev parent reply other threads:[~2014-06-25 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 10:21 [net-next PATCH v3 0/2] bridge: more efficient fdb dumping Jamal Hadi Salim
2014-06-25 10:21 ` [net-next PATCH v3 1/2] bridge: fdb dumping takes a filter device Jamal Hadi Salim
2014-06-25 10:21 ` [net-next PATCH v3 2/2] bridge: netlink dump interface at par with brctl Jamal Hadi Salim
2014-06-27 0:45 ` David Miller
2014-06-25 10:25 ` Jamal Hadi Salim [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=53AAA38D.8090808@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
--cc=vyasevic@redhat.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.