From: Johannes Berg <johannes@sipsolutions.net>
To: Chaitanya <chaitanyatk@posedge.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Fix the MAX MTU calculation
Date: Fri, 21 Dec 2012 15:11:23 +0100 [thread overview]
Message-ID: <1356099083.9580.7.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50D44BCC.30304@posedge.com>
On Fri, 2012-12-21 at 17:15 +0530, Chaitanya wrote:
> Fix the Max MTU calculations.
> Do not take headers in to account, only MAX MSDU size
> as per 802.11-2012(8.2.3) is enough.
Applied, but I rewrote the changelog a bit,
> ToDo: Add support for AMSDU in future.
removed this (AMSDU is irrelevant here)
> - int meshhdrlen;
> - struct ieee80211_sub_if_data *sdata = IEEE80211_DEV_TO_SUB_IF(dev);
> -
> - meshhdrlen = (sdata->vif.type == NL80211_IFTYPE_MESH_POINT) ? 5 : 0;
> + /* 802.11-2012: 8.2.3: The maximum frame body size is determined by
> + 1. The maximum MSDU size (2304 octets),
> + 2. plus the length of the Mesh Control field (6, 12, or 18 octets)
> + if present,
> + 3. the maximum unencrypted MMPDU size excluding the MAC header and
> + FCS (2304 octets) or
> + 4. the maximum A- MSDU size (3839 or 7935 octets),
> + plus any overhead from security encapsulation.
> + Note1: IEEE80211_MAX_DATA_LEN doesnt include any headers (2304),
> + so it can be used directly+ Mesh HDR Len
> + Note2: In Other places (skb_alloc) its handled properly.
> +
> + ToDO: Make the MAX_DATA_LEN driver configurable through its
> + AMSDU capabilities.
> + */
and I also removed the big comment that doesn't really apply
johannes
prev parent reply other threads:[~2012-12-21 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201212211141.qBLBfZdq015078@chaitanya-desktop>
2012-12-21 11:45 ` [PATCH] mac80211: Fix the MAX MTU calculation Chaitanya
2012-12-21 14:11 ` Johannes Berg [this message]
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=1356099083.9580.7.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chaitanyatk@posedge.com \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.