From: Jamal Hadi Salim <jhs@mojatatu.com>
To: vyasevic@redhat.com, davem@davemloft.net, stephen@networkplumber.org
Cc: netdev@vger.kernel.org, sfeldma@cumulusnetworks.com,
john.r.fastabend@intel.com, roopa@cumulusnetworks.com
Subject: Re: [net-next PATCH 2/2] bridge: netlink dump interface at par with brctl
Date: Sun, 15 Jun 2014 11:28:53 -0400 [thread overview]
Message-ID: <539DBBB5.3000906@mojatatu.com> (raw)
In-Reply-To: <53970745.7040002@redhat.com>
On 06/10/14 09:25, Vlad Yasevich wrote:
>
> I gave it some thought and I think something like the following
> pseudo-code would work.
>
> dump_dev_fdbs(dev, filter)
> {
> if (dev->dumper)
> dev->ndo_dumper(dev, filter);
> else
> default_dumper(dev, filter);
> }
>
> for_each_netdev() {
> if (bridge_filter) {
> if (dev->index != bridge_filter)
> skip;
>
> dump_dev_fdbs(dev, port_filter);
> } else {
> if (port_filter) {
> if (bridge_port &&
> dev->index != port_filter)
> skip;
>
> }
>
> if (bridge_port) {
> br_dev = get_bridge();
> dump_dev_fdbs(br_dev, port_filter);
> }
>
> dump_dev_fdbs(dev, port_filter);
> }
> }
>
>
> What do you think?
Too bad i missed the net-next submission.
I am not sure what you suggest above will improve upon readability,
but i will take another run at it when Dave opens up.
I know reading the patch was hard - the code was not as bad.
We'll see.
cheers,
jamal
next prev parent reply other threads:[~2014-06-15 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 14:27 [net-next PATCH 1/2] bridge: fdb dumping takes a filter device Jamal Hadi Salim
2014-06-07 14:27 ` [net-next PATCH 2/2] bridge: netlink dump interface at par with brctl Jamal Hadi Salim
2014-06-07 14:34 ` Jamal Hadi Salim
2014-06-11 6:44 ` David Miller
2014-06-09 16:41 ` Vlad Yasevich
2014-06-10 11:41 ` Jamal Hadi Salim
2014-06-10 13:25 ` Vlad Yasevich
2014-06-15 15:28 ` Jamal Hadi Salim [this message]
2014-06-24 14:18 ` Jamal Hadi Salim
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=539DBBB5.3000906@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=davem@davemloft.net \
--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.