From: Vlad Yasevich <vyasevic@redhat.com>
To: Cong Wang <cwang@twopensource.com>,
Vladislav Yasevich <vyasevich@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
netdev <netdev@vger.kernel.org>,
"bridge@lists.linux-foundation.org"
<bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] [PATCH v3 net-next 3/3] bridge: Add filtering support for default_pvid
Date: Fri, 03 Oct 2014 09:37:27 -0400 [thread overview]
Message-ID: <542EA697.7070109@redhat.com> (raw)
In-Reply-To: <CAHA+R7OycteYron5K3YJ3qtsEE-5uUxhPkictJDWosXCihR5hA@mail.gmail.com>
On 10/03/2014 12:41 AM, Cong Wang wrote:
> On Thu, Oct 2, 2014 at 4:54 PM, Vladislav Yasevich <vyasevich@gmail.com> wrote:
>> +static void br_vlan_disable_default_pvid(struct net_bridge *br)
>> +{
>> + struct net_bridge_port *p;
>> + u16 pvid = br->default_pvid;
>> +
>> + /* Disable default_pvid on all ports where it is still
>> + * configured.
>> + */
>> +
>
> This empty line is not necessary.
>
>> + if (vlan_default_pvid(br_get_vlan_info(br), pvid))
>> + br_vlan_delete(br, pvid);
>> +
>> + list_for_each_entry(p, &br->port_list, list) {
>> + if (vlan_default_pvid(nbp_get_vlan_info(p), pvid))
>> + nbp_vlan_delete(p, pvid);
>> + }
>> +
>> + br->default_pvid = 0;
>> +}
>> +
>> +static int __br_vlan_set_default_pvid(struct net_bridge *br, u16 pvid)
>> +{
>> + struct net_bridge_port *p;
>> + u16 old_pvid;
>> + int err;
>> + DECLARE_BITMAP(changed, BR_MAX_PORTS);
>
>
> This bitmap will use 128 bytes on stack, why not using heap?
>
I suppose I wanted to avoid yet another memory allocation failure condition.
Is this really going to cause issues?
Thanks
-vlad
>> +
>> + bitmap_zero(changed, BR_MAX_PORTS);
>> +
>> + /* This function runs with filtering turned off so we can
>> + * remove the old pvid configuration and add the new one after
>> + * without impacting traffic.
>> + */
>> +
>> + old_pvid = br->default_pvid;
>
>
> Remove the empty line.
>
> [...]
>
>> +int nbp_vlan_init(struct net_bridge_port *p)
>> +{
>> + int rc = 0;
>> +
>> + if (p->br->default_pvid) {
>> + rc = nbp_vlan_add(p, p->br->default_pvid,
>> + BRIDGE_VLAN_INFO_PVID |
>> + BRIDGE_VLAN_INFO_UNTAGGED);
>> + }
>> +
>> + return rc;
>> +}
>
> 'rc' can be removed.
>
next prev parent reply other threads:[~2014-10-03 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 23:54 [Bridge] [PATCH v3 net-next 0/3] bridge: Add vlan filtering support for default pvid Vladislav Yasevich
2014-10-02 23:54 ` [Bridge] [PATCH v3 net-next 1/3] bridge: Add a default_pvid sysfs attribute Vladislav Yasevich
2014-10-03 1:08 ` Toshiaki Makita
2014-10-03 13:42 ` Vlad Yasevich
2014-10-03 14:31 ` Toshiaki Makita
2014-10-02 23:54 ` [Bridge] [PATCH v3 net-next 2/3] bridge: Simplify pvid checks Vladislav Yasevich
2014-10-03 1:11 ` Toshiaki Makita
2014-10-02 23:54 ` [Bridge] [PATCH v3 net-next 3/3] bridge: Add filtering support for default_pvid Vladislav Yasevich
2014-10-03 1:11 ` Toshiaki Makita
2014-10-03 4:41 ` Cong Wang
2014-10-03 13:37 ` Vlad Yasevich [this message]
2014-10-03 16:42 ` Cong Wang
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=542EA697.7070109@redhat.com \
--to=vyasevic@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=cwang@twopensource.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vyasevich@gmail.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).