From: matthieu castet <castet.matthieu@free.fr>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jiri Benc <jbenc@suse.cz>,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org
Subject: Re: softmac mtu
Date: Wed, 27 Sep 2006 19:17:09 +0200 [thread overview]
Message-ID: <451AB215.3080500@free.fr> (raw)
In-Reply-To: <1159365316.2698.40.camel@ux156>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
Johannes Berg wrote:
> On Wed, 2006-09-27 at 15:57 +0200, castet.matthieu@free.fr wrote:
>
>
>>Also I wonder what should be the max mtu.
>
>
> 2304, I think, as that's
> synonym sMaxMsduLng Integer = 2304; /* max octets in an MSDU */
>
Yes but if it is bigger the frame get framented at the 802.11 layer : in
theory we could put mtu (IP max packet size) a big as we want [1].
Also if I understand it correctly if encryption is used there is less
space for IP data ?
If people want to play with it, I attach the current version of my
(trivial) patch.
Matthieu
[1]
if mtu > 2304, (struct ieee80211_txb*)->nr_frags is bigger than one ;)
[-- Attachment #2: ieee80211mtu --]
[-- Type: text/plain, Size: 759 bytes --]
Index: linux/net/ieee80211/ieee80211_module.c
===================================================================
--- linux.orig/net/ieee80211/ieee80211_module.c 2006-09-25 22:37:20.000000000 +0200
+++ linux/net/ieee80211/ieee80211_module.c 2006-09-25 22:39:07.000000000 +0200
@@ -118,6 +118,14 @@
&ieee->network_free_list);
}
+static int ieee80211_change_mtu(struct net_device *dev, int new_mtu)
+{
+ if ((new_mtu < 68) || (new_mtu > 2400))
+ return -EINVAL;
+ dev->mtu = new_mtu;
+ return 0;
+}
+
struct net_device *alloc_ieee80211(int sizeof_priv)
{
struct ieee80211_device *ieee;
@@ -133,6 +141,7 @@
}
ieee = netdev_priv(dev);
dev->hard_start_xmit = ieee80211_xmit;
+ dev->change_mtu = ieee80211_change_mtu;
ieee->dev = dev;
next prev parent reply other threads:[~2006-09-27 17:17 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 [this message]
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
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=451AB215.3080500@free.fr \
--to=castet.matthieu@free.fr \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--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;
as well as URLs for NNTP newsgroup(s).