From: Eric Dumazet <eric.dumazet@gmail.com>
To: Patrick McHardy <kaber@trash.net>
Cc: "David S. Miller" <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH 4/6] vlan: Optimize multiple unregistration
Date: Wed, 28 Oct 2009 21:47:35 +0100 [thread overview]
Message-ID: <4AE8ADE7.1010909@gmail.com> (raw)
In-Reply-To: <4AE8A425.1000600@trash.net>
Patrick McHardy a écrit :
> Eric Dumazet wrote:
>> Use unregister_netdevice_many() to speedup master device unregister.
>>
>> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
>> ---
>> include/linux/if_vlan.h | 1
>> net/8021q/vlan.c | 49 +++++++++++++++++++++++++-------------
>> net/core/dev.c | 1
>> 3 files changed, 35 insertions(+), 16 deletions(-)
>>
>> diff --git a/include/linux/if_vlan.h b/include/linux/if_vlan.h
>> index 8898cbe..71a4870 100644
>> --- a/include/linux/if_vlan.h
>> +++ b/include/linux/if_vlan.h
>> @@ -85,6 +85,7 @@ struct vlan_group {
>> * the vlan is attached to.
>> */
>> unsigned int nr_vlans;
>> + int killall;
>> struct hlist_node hlist; /* linked list */
>> struct net_device **vlan_devices_arrays[VLAN_GROUP_ARRAY_SPLIT_PARTS];
>> struct rcu_head rcu;
>> diff --git a/net/8021q/vlan.c b/net/8021q/vlan.c
>> index 6b5c9dd..511afe7 100644
>> --- a/net/8021q/vlan.c
>> +++ b/net/8021q/vlan.c
>> @@ -159,11 +159,12 @@ void unregister_vlan_dev(struct net_device *dev, struct list_head *head)
>> if (real_dev->features & NETIF_F_HW_VLAN_FILTER)
>> ops->ndo_vlan_rx_kill_vid(real_dev, vlan_id);
>>
>> - vlan_group_set_device(grp, vlan_id, NULL);
>> grp->nr_vlans--;
>>
>> - synchronize_net();
>> -
>> + if (!grp->killall) {
>> + vlan_group_set_device(grp, vlan_id, NULL);
>> + synchronize_net();
>> + }
>> unregister_netdevice_queue(dev, head);
>>
>> /* If the group is now empty, kill off the group. */
>> @@ -183,6 +184,34 @@ void unregister_vlan_dev(struct net_device *dev, struct list_head *head)
>> dev_put(real_dev);
>> }
>>
>> +void unregister_vlan_dev_alls(struct vlan_group *grp)
>
> This could be static.
>
>> +{
>> + LIST_HEAD(list);
>> + int i;
>> + struct net_device *vlandev;
>> + struct vlan_group save;
>> +
>> + memcpy(&save, grp, sizeof(save));
>> + memset(&grp->vlan_devices_arrays, 0, sizeof(grp->vlan_devices_arrays));
>
> This shouldn't be necessary since the lower device is already in the
> process of being unregistered. If it was necessary, it could cause
> crashes since the individual pointers are not set to zero atomically.
> Or maybe I'm misunderstanding the purpose entirely :)
Very good point indeed, even if in practice memset() use long word transferts
I'll make a cleanup patch, or do you want to do it ?
next prev parent reply other threads:[~2009-10-28 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 17:06 [PATCH 4/6] vlan: Optimize multiple unregistration Eric Dumazet
2009-10-28 20:05 ` Patrick McHardy
2009-10-28 20:47 ` Eric Dumazet [this message]
2009-10-29 13:45 ` Patrick McHardy
2009-10-29 14:23 ` Patrick McHardy
2009-10-29 14:30 ` Eric Dumazet
2009-10-29 14:33 ` Patrick McHardy
2009-10-29 14:43 ` Eric Dumazet
2009-10-29 17:25 ` Patrick McHardy
2009-10-30 6:30 ` Eric Dumazet
2009-10-30 6:43 ` 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=4AE8ADE7.1010909@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/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).