From: Johan Hedberg <johan.hedberg@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 1/6] Bluetooth: 6lowpan: Fix imtu & omtu values
Date: Tue, 6 Oct 2015 13:03:19 +0300 [thread overview]
Message-ID: <1444125804-15577-2-git-send-email-johan.hedberg@gmail.com> (raw)
In-Reply-To: <1444125804-15577-1-git-send-email-johan.hedberg@gmail.com>
From: Johan Hedberg <johan.hedberg@intel.com>
The omtu value is determined by the remote peer so there's no point in
trying to hard-code it to any value. The IPSP specification otoh gives
a more reasonable value for the imtu, i.e. 1280.
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
---
net/bluetooth/6lowpan.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/net/bluetooth/6lowpan.c b/net/bluetooth/6lowpan.c
index 131e79cde350..3e20f7a60d61 100644
--- a/net/bluetooth/6lowpan.c
+++ b/net/bluetooth/6lowpan.c
@@ -775,8 +775,7 @@ static struct l2cap_chan *chan_create(void)
chan->chan_type = L2CAP_CHAN_CONN_ORIENTED;
chan->mode = L2CAP_MODE_LE_FLOWCTL;
- chan->omtu = 65535;
- chan->imtu = chan->omtu;
+ chan->imtu = 1280;
return chan;
}
--
2.4.3
next prev parent reply other threads:[~2015-10-06 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 10:03 [PATCH 0/6] Bluetooth: 6lowpan cleanups Johan Hedberg
2015-10-06 10:03 ` Johan Hedberg [this message]
2015-10-06 10:03 ` [PATCH 2/6] Bluetooth: 6lowpan: Remove redundant (and incorrect) MPS assignments Johan Hedberg
2015-10-06 10:03 ` [PATCH 3/6] Bluetooth: 6lowpan: Remove redundant BT_CONNECTED assignment Johan Hedberg
2015-10-06 10:03 ` [PATCH 4/6] Bluetooth: 6lowpan: Remove unnecessary chan_open() function Johan Hedberg
2015-10-06 10:03 ` [PATCH 5/6] Bluetooth: 6lowpan: Rename confusing 'pchan' variables Johan Hedberg
2015-10-06 10:03 ` [PATCH 6/6] Bluetooth: 6lowpan: Remove unnecessary chan_get() function Johan Hedberg
2015-10-06 10:25 ` [PATCH 0/6] Bluetooth: 6lowpan cleanups Jukka Rissanen
2015-10-08 8:46 ` Marcel Holtmann
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=1444125804-15577-2-git-send-email-johan.hedberg@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@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).