From: "Florian Fainelli" <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: amwang@redhat.com, jiri@resnulli.us, stephen@networkplumber.org,
kaber@trash.net, davem@davemloft.net, vyasevic@redhat.com,
johannes@sipsolutions.net, eric.dumazet@gmail.com,
"Florian Fainelli" <f.fainelli@gmail.com>
Subject: [PATCH 2/3] net: vlan: handle NETDEV_CHANGEROOM events
Date: Tue, 20 Aug 2013 13:45:51 +0100 [thread overview]
Message-ID: <1377002752-4622-3-git-send-email-f.fainelli@gmail.com> (raw)
In-Reply-To: <1377002752-4622-1-git-send-email-f.fainelli@gmail.com>
Whenever the parent device has needed_headroom/needed_tailroom
requirement changes, the VLAN devices should also be updated to the new
value. Handle the NETDEV_CHANGEROOM events and just set the new headroom
and tailroom requirements to the values of the parent device.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
---
net/8021q/vlan.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/net/8021q/vlan.c b/net/8021q/vlan.c
index 61fc573..11a1faa 100644
--- a/net/8021q/vlan.c
+++ b/net/8021q/vlan.c
@@ -466,6 +466,13 @@ static int vlan_device_event(struct notifier_block *unused, unsigned long event,
vlan_group_for_each_dev(grp, i, vlandev)
call_netdevice_notifiers(event, vlandev);
break;
+
+ case NETDEV_CHANGEROOM:
+ vlan_group_for_each_dev(grp, i, vlandev) {
+ dev_set_headroom(vlandev, dev->needed_headroom);
+ dev_set_tailroom(vlandev, dev->needed_tailroom);
+ }
+ break;
}
out:
--
1.8.1.2
next prev parent reply other threads:[~2013-08-20 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 12:45 [PATCH 0/3] net: propagate dynamic needed_headroom/tailroom changes Florian Fainelli
2013-08-20 12:45 ` [PATCH 1/3] net: add a new NETDEV_CHANGEROOM event type Florian Fainelli
2013-08-20 15:16 ` Johannes Berg
2013-08-20 15:30 ` Florian Fainelli
2013-08-20 16:10 ` Jiri Pirko
2013-08-20 16:35 ` Johannes Berg
2013-08-20 17:30 ` Florian Fainelli
2013-08-20 12:45 ` Florian Fainelli [this message]
2013-08-20 12:45 ` [PATCH 3/3] net: bridge: handle NETDEV_CHANGEROOM event Florian Fainelli
2013-08-20 13:29 ` [PATCH 0/3] net: propagate dynamic needed_headroom/tailroom changes Jiri Pirko
2013-08-20 14:24 ` Florian Fainelli
2013-08-20 14:27 ` Jiri Pirko
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=1377002752-4622-3-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--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 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).