netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: Jiri Benc <jbenc@suse.cz>,
	"John W. Linville" <linville@tuxdriver.com>,
	netdev@vger.kernel.org, castet.matthieu@free.fr
Subject: Re: softmac mtu
Date: Thu, 28 Sep 2006 17:47:12 +0200	[thread overview]
Message-ID: <1159458432.2648.38.camel@ux156> (raw)
In-Reply-To: <200609281735.17616.mb@bu3sch.de>

On Thu, 2006-09-28 at 17:35 +0200, Michael Buesch wrote:

> I am pretty sure this is the maximum _fragment_ size.

But then why does it talk of MPDU and MSDU?

from 802.11:

synonym sMaxMsduLng Integer = 2304; /* max octets in an MSDU */

synonym sMaxMpduLng Integer =         /* max octets in an MPDU */
  (sMaxMsduLng + sMacHdrLng + sWdsAddLng + sWepAddLng + sCrcLng);

synonym sMinFragLng Integer = 256; /* min value for aMpduMaxLength */
synonym sMaxFragNum Integer =        /* maximum fragment number */
  (sMaxMsduLng / (sMinFragLng - sMacHdrLng - sCrcLng));

The last calculation implies that each frame can only be up to
sMaxMsduLng octets long even when fragmented.

also cf. 9.1.4:

   9.1.4 Fragmentation/defragmentation overview

   The process of partitioning a MAC service data unit (MSDU) or a MAC
   management protocol data unit (MMPDU) into smaller MAC level frames,
   MAC protocol data units (MPDUs), is called fragmentation.
   Fragmentation creates MPDUs smaller than the original MSDU or MMPDU
   length to increase reliability, by increasing the probability of
   successful transmission of the MSDU or MMPDU in cases where channel
   characteristics limit reception reliability for longer frames.

IOW, I read it as an MSDU is the data that is supposed to be transmitted
over the link and that can be at most 2304 bytes long, and then it may
be fragmented or not and is then copied into (an) MPDU(s).

> But each packet (which max size is defined by the MTU) can
> be fragmented. I don't know if there's a limit on the max
> number of frags.

There's only a 4 bit fragment counter ;) However, see above.

johannes

  parent reply	other threads:[~2006-09-28 15:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23 17:50 softmac mtu Matthieu CASTET
2006-09-23 21:40 ` Larry Finger
2006-09-23 21:47   ` David Miller
2006-09-23 21:59     ` Larry Finger
     [not found]       ` <39e6f6c70609231504qd442c59hebf152df00a7af0c@mail.gmail.com>
2006-09-23 22:08         ` Arnaldo Carvalho de Melo
2006-09-23 22:23       ` David Miller
2006-09-25 19:17 ` Matthieu CASTET
2006-09-25 20:01   ` John W. Linville
2006-09-27 12:39     ` Jiri Benc
2006-09-27 13:57       ` castet.matthieu
2006-09-27 13:55         ` Johannes Berg
2006-09-27 17:17           ` matthieu castet
2006-09-28  7:39             ` Johannes Berg
2006-09-28 17:58               ` matthieu castet
2006-09-28 15:35           ` Michael Buesch
2006-09-28 15:45             ` Jouni Malinen
2006-09-28 15:47             ` Johannes Berg [this message]
2006-09-28 16:13               ` Jouni Malinen
2006-09-28 17:02         ` Daniel Drake
  -- strict thread matches above, loose matches on Subject: below --
2006-09-23 17:50 Matthieu CASTET

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=1159458432.2648.38.camel@ux156 \
    --to=johannes@sipsolutions.net \
    --cc=castet.matthieu@free.fr \
    --cc=jbenc@suse.cz \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --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).