From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] omtu, imtu
Date: Wed, 09 Feb 2005 16:18:03 +0100 [thread overview]
Message-ID: <1107962283.13863.65.camel@pegasus> (raw)
In-Reply-To: <20050209160702.56b74881@CleverSophie>
Hi Bjoern,
> can you also tell me what omtu and imtu are for? I know the Maximum Transfer Unit, but what exactly do these 2? I have set them to 672 and 0 like in the rctest.c file.
what about reading the L2CAP part of the Bluetooth specification. It is
all there, but in short (i)ncoming MTU and (o)utgoing MTU.
> Is 672 the maximum? It would just be nice to know the maximum data per frame, for a good header to data proportion.
The maximal value is 65535. The header/payload is not important for the
throughput. Only matching it to the baseband packet types helps.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-02-09 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 13:07 [Bluez-devel] btohs,btohl, # Björn Specht #
2005-02-09 13:19 ` Marcel Holtmann
2005-02-09 13:38 ` # Björn Specht #
2005-02-09 13:57 ` Marcel Holtmann
2005-02-09 14:00 ` # Björn Specht #
2005-02-09 15:07 ` [Bluez-devel] omtu, imtu # Björn Specht #
2005-02-09 15:18 ` 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=1107962283.13863.65.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.