From: Johannes Berg <johannes@sipsolutions.net>
To: Charles Gordon <digigordo@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Fragmentation
Date: Thu, 02 Apr 2009 03:55:29 +0200 [thread overview]
Message-ID: <1238637329.4141.7.camel@johannes.local> (raw)
In-Reply-To: <86201b3f0904011355p788ee867p300b5be24569e46b@mail.gmail.com> (sfid-20090401_225534_289155_7CA4C47F)
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
Charles,
> I'm working on a driver which will use mac80211. My hardware cannot
> transmit a frame larger than 1792 bytes, or receive frames larger than
> 2048 bytes. Right now I am relying on the fragmentation routines
> built into mac80211. Is there a way for my driver to tell mac80211
> what the maximum transmit and receive frame sizes are? Do I need to
> implement my own fragmentation code to handle this?
Using fragmentation for this is not a good plan -- better adjust the
maximum MTU. We currently cannot do that because mac80211 assumes that
all devices actually conform to the 802.11 standard wrt. this... Clearly
your device does not -- 2048 bytes is much too small, and you cannot
force the remote peer to send smaller frames than that (though in
practise it they will be smaller most of the time).
I would suggest that for now you don't worry about it at all -- the
default MTU is 1500 matching ethernet, so the largest frame that
mac80211 will give you by default is much smaller than 1792 bytes. Then,
once you release your driver under GPL and post it for inclusion into
our tree we can think about adding a new hardware capability to mac80211
that restricts users from increasing the MTU above 1792-30-2-8-4 (or
something like that).
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-04-02 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 20:55 Fragmentation Charles Gordon
2009-04-02 1:55 ` 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=1238637329.4141.7.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=digigordo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox