From: Marcel Holtmann <marcel@holtmann.org>
To: Aaron Klish <aklish1@urbana.css.mot.com>
Cc: Aaron Klish <aklish1@wombat.urbana.css.mot.com>,
Aaron Klish <AKLISH1@motorola.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RFCOMM TTY data loss
Date: Thu, 23 Oct 2003 08:03:46 +0200 [thread overview]
Message-ID: <1066889032.18996.28.camel@pegasus> (raw)
In-Reply-To: <Pine.GSO.4.20.0310221044310.1278-100000@angel.urbana.css.mot.com>
Hi Aaron,
> Are there any plans in the future to allow control of RFCOMM MTU and credits from user space?
> I'm using 2.4.20 (mh9 patch) and these parameters are currently assigned default values in the kernel.
> L2CAP already has an option to control MTU through setsockopt. It seems like adding control
> for parameters for RFCOMM would be a good feature - perhaps also through setsockopt? Any thoughts
> on this? Thanks.
the Linux implementation of RFCOMM is a stream and so it don't have a
MTU. You have the in and out MTU of the underlaying L2CAP PSM 3 and we
try to set them to 1024 by default. We have talked about this some time
ago (look at the archive) and there is no proof that having a different
L2CAP MTU improves the performance of RFCOMM.
The credits are not for the user space, because they are only used for
the flow control. These kind of stuff must be handled by the RFCOMM
layer and nobody should have to worry about it. If there is a problem
with it, we have to fix it in the RFCOMM layer itself.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-10-23 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 21:51 [Bluez-devel] RFCOMM TTY data loss Aaron Klish
2003-10-21 12:09 ` Marcel Holtmann
2003-10-22 15:17 ` Aaron Klish
2003-10-22 15:51 ` Aaron Klish
2003-10-23 6:03 ` Marcel Holtmann [this message]
2003-10-23 22:08 ` setsockopt for RFCOMM Aaron Klish
2003-10-24 6:24 ` [Bluez-devel] " 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=1066889032.18996.28.camel@pegasus \
--to=marcel@holtmann.org \
--cc=AKLISH1@motorola.com \
--cc=aklish1@urbana.css.mot.com \
--cc=aklish1@wombat.urbana.css.mot.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox