netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, amwang@redhat.com,
	stephen@networkplumber.org, kaber@trash.net, davem@davemloft.net,
	vyasevic@redhat.com, johannes@sipsolutions.net,
	eric.dumazet@gmail.com
Subject: Re: [PATCH 0/3] net: propagate dynamic needed_headroom/tailroom changes
Date: Tue, 20 Aug 2013 15:29:50 +0200	[thread overview]
Message-ID: <20130820132950.GA1593@minipsycho.brq.redhat.com> (raw)
In-Reply-To: <1377002752-4622-1-git-send-email-f.fainelli@gmail.com>

Tue, Aug 20, 2013 at 02:45:49PM CEST, f.fainelli@gmail.com wrote:
>Hi all,
>
>This patchset aims at allowing dynamically changing a given device
>needed_headroom/tailroom space and propagating such events to stacked
>devices such as bridges and vlans.

You should also add support for other stacked devices, like bonding,
team, macvlan, ovs-datapath, etc.	
	
>
>Unless callers use the new helpers (dev_set_headroom/dev_set_tailroom)
>there is no functional change introduced.
>
>I tested this with an out of tree Ethernet driver with both VLANs and
>bridges and the need for a 64-byte headroom to insert a transmit
>status descriptor in front of a SKB.

Would be nice to add at least one driver which would use your new api.

Thanks,
	Jiri

>
>Since I am not familiar with all subsystems/drivers changing the
>needed_headroom/tailroom requirements, I would leave that to them.
>
>Florian Fainelli (3):
>  net: add a new NETDEV_CHANGEROOM event type
>  net: vlan: handle NETDEV_CHANGEROOM events
>  net: bridge: handle NETDEV_CHANGEROOM event
>
> include/linux/netdevice.h |  3 +++
> net/8021q/vlan.c          |  7 +++++++
> net/bridge/br_if.c        | 32 ++++++++++++++++++++++++++++++++
> net/bridge/br_notify.c    |  5 +++++
> net/bridge/br_private.h   |  2 ++
> net/core/dev.c            | 46 ++++++++++++++++++++++++++++++++++++++++++++++
> 6 files changed, 95 insertions(+)
>
>-- 
>1.8.1.2
>
>

  parent reply	other threads:[~2013-08-20 13:29 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 ` [PATCH 2/3] net: vlan: handle NETDEV_CHANGEROOM events Florian Fainelli
2013-08-20 12:45 ` [PATCH 3/3] net: bridge: handle NETDEV_CHANGEROOM event Florian Fainelli
2013-08-20 13:29 ` Jiri Pirko [this message]
2013-08-20 14:24   ` [PATCH 0/3] net: propagate dynamic needed_headroom/tailroom changes 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=20130820132950.GA1593@minipsycho.brq.redhat.com \
    --to=jiri@resnulli.us \
    --cc=amwang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=f.fainelli@gmail.com \
    --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).