From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] mac80211: assign needed_headroom/tailroom for netdevs
Date: Sun, 04 May 2008 23:31:18 +0200 [thread overview]
Message-ID: <1209936678.7304.14.camel@johannes.berg> (raw)
In-Reply-To: <1209936253.7304.10.camel@johannes.berg> (sfid-20080504_232356_925288_0C998746)
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
On Sun, 2008-05-04 at 23:24 +0200, Johannes Berg wrote:
> This assigns the netdev's needed_headroom/tailroom members
> to take advantage of pre-allocated space for 802.11 headers.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> ---
> Builds on my other patch to add those fields, of course!
>
> net/mac80211/iface.c | 8 ++++++++
> net/mac80211/tx.c | 14 +++++++++-----
> 2 files changed, 17 insertions(+), 5 deletions(-)
>
> --- everything.orig/net/mac80211/iface.c 2008-05-04 15:40:53.000000000 +0200
> +++ everything/net/mac80211/iface.c 2008-05-04 16:08:45.000000000 +0200
> @@ -53,6 +53,14 @@ int ieee80211_if_add(struct net_device *
> if (!ndev)
> return -ENOMEM;
>
> + ndev->needed_headroom = local->tx_headroom +
> + 4*6 /* four MAC addresses */
> + + 2 + 2 + 2 + 2 /* ctl, dur, seq, qos */
> + + 6 /* mesh */
> + - ETH_HLEN /* ethernet hard_header_len */
> + + IEEE80211_ENCRYPT_HEADROOM;
Although this seems to have worked for me, that was most likely
coincidence because I had two bytes extra headroom and no fourth MAC
address, I actually forgot 8 bytes here (rfc1042/bridge tunnel
encapsulation)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-05-04 21:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 21:24 [RFC] mac80211: assign needed_headroom/tailroom for netdevs Johannes Berg
2008-05-04 21:31 ` Johannes Berg [this message]
2008-05-04 21:32 ` [RFC v2] " Johannes Berg
2008-05-05 0:30 ` David Miller
2008-05-05 7:22 ` Johannes Berg
2008-05-05 14:27 ` Tomas Winkler
2008-05-05 15:22 ` Johannes Berg
2008-05-05 17:15 ` Tomas Winkler
2008-05-05 17:57 ` Johannes Berg
2008-05-05 18:58 ` David Miller
2008-05-05 19:05 ` Johannes Berg
2008-05-05 19:50 ` David Miller
2008-05-05 19:57 ` Johannes Berg
2008-05-05 20:02 ` David Miller
2008-05-05 20:10 ` Johannes Berg
2008-05-05 20:44 ` David Miller
2008-05-05 20:57 ` Johannes Berg
2008-05-05 21:01 ` David Miller
2008-05-05 22:37 ` David Miller
2008-05-05 22:44 ` Johannes Berg
2008-05-05 23:14 ` David Miller
2008-05-05 23:23 ` Johannes Berg
2008-05-05 23:39 ` David Miller
2008-05-06 0:01 ` Johannes Berg
2008-05-06 0:08 ` David Miller
2008-05-06 11:13 ` Johannes Berg
2008-05-06 1:32 ` Herbert Xu
2008-05-13 5:01 ` David Miller
2008-05-05 23:03 ` David Miller
2008-05-05 23:17 ` Johannes Berg
2008-05-05 23:24 ` David Miller
2008-05-05 23:30 ` Johannes Berg
2008-05-05 23:36 ` Johannes Berg
2008-05-05 23:40 ` David Miller
2008-05-13 3:52 ` David Miller
2008-05-13 9:01 ` Johannes Berg
2008-05-13 9:45 ` David Miller
2008-05-13 10:07 ` Johannes Berg
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=1209936678.7304.14.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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