All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: linux-bluetooth@vger.kernel.org
Subject: RFCOMM connection lag (slow)
Date: Sun, 24 Jul 2011 18:22:38 +0200	[thread overview]
Message-ID: <4E2C46CE.2060000@kernelconcepts.de> (raw)

Hi!
I recently found a strange behaviour...

I have a device which accepts an RFCOMM connection on channel 1.
Creating the connection works just fine and I can basically communicate.

But as soon as larger chunks of data are sent (something like 128 bytes
at a time) it starts to take a pretty long time to transfer it (in the
range of about a second). The connection stays connected and data can be
sent but at a very slow pace.
This is from a 2.6.39 kernel to the device, my PC has a Bluetooth3.0 USB
device.

The interesting part is that if I try the same thing from an HTC G1
phone it works as expected, i.e. "fast". I tried to compare the HCI
settings between the HTC G1 and my notebook and did the same on my
notebook which did not help (the only obvious difference was disabled
PARK mode and a slightly different ACL MTU).

It is pretty likely that the device also has an RFCOMM bug here but
since it works with the HTC phone it must be possible to make it work
with my notebook too.

Any hint would be very much appreciated ;)

Thanks!

Cheers
  nils

-- 
kernel concepts GbR        Tel: +49-271-771091-12
Sieghuetter Hauptweg 48
D-57072 Siegen             Mob: +49-176-21024535
http://www.kernelconcepts.de

             reply	other threads:[~2011-07-24 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-24 16:22 Nils Faerber [this message]
2011-07-24 17:06 ` RFCOMM connection lag (slow) Peter Hurley
2011-07-24 17:58   ` Nils Faerber
2011-07-24 18:42     ` Nils Faerber
2011-07-24 19:20       ` Peter Hurley
2011-07-26  8:42         ` Nils Faerber

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=4E2C46CE.2060000@kernelconcepts.de \
    --to=nils.faerber@kernelconcepts.de \
    --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 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.