From: Marcel Holtmann <marcel@holtmann.org>
To: "Nicholas A. Preyss" <nalp@gmx.net>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] MTU and MRU for Bluetooth
Date: Wed, 05 May 2004 22:50:31 +0200 [thread overview]
Message-ID: <1083790231.4420.40.camel@pegasus> (raw)
In-Reply-To: <20040505211012.GA11210@gmx.net>
Hi Nicholas,
> I think, he wants a MTU size that doesn't lead to fragmentation on the
> carrying transport medium. I think this doesn't make much sense due to
> the "short" packets of bluetooth, and the fact that L2CAP packets can be
> up to 2^16 bytes large.
actually there is no proof that choosing a different MTU on the L2CAP
level gives you any performance improvements. However a too small MTU
decreases the performance and this is why we are using 1024 even if 672
is the default MTU. Some time ago we discussed this and until now nobody
really proofed that a different MTU is better or that we should make the
L2CAP MTU for RFCOMM configurable, because some upper layer will improve
if we do so. Proof it to me and we will see ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-05-05 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 19:27 [Bluez-users] MTU and MRU for Bluetooth Florian
2004-05-04 17:43 ` Marcel Holtmann
2004-05-05 21:10 ` Nicholas A. Preyss
2004-05-05 20:50 ` Marcel Holtmann [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=1083790231.4420.40.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=nalp@gmx.net \
/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