public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: suraj <suraj@atheros.com>
To: <linux-bluetooth@vger.kernel.org>
Cc: <Luis.Rodriguez@Atheros.com>, <Jothikumar.Mothilal@Atheros.com>
Subject: buffer starvation with multiple ACL link
Date: Thu, 6 May 2010 13:15:32 +0530	[thread overview]
Message-ID: <1273131932.2229.9.camel@atheros013-desktop> (raw)
In-Reply-To: <1273062798.19162.6.camel@atheros013-desktop>

Hi,

I am seeing a strange issue with multiple ACL connection with CSR chip.

I am having 2 ACL link, one with FTP going on and another streaming
A2DP. 
The moment the A2DP link goes out of range ,I see that the FTP also
stops. It resumes as soon as A2DP comes back in range.

On further analysis I could verify that since the A2DP link is
blocked( due to remote being OoR) the controller's ACL buffers with A2DP
data are stuck. 
But at the host level this is not considered and Bluez keeps sending
A2DP data until it blocks all the ACL buffers which in turns blocks FTP
also.

I was expecting controller to flush these packets sometime and free the
A2DP buffers. Not sure, what is the default Flush timeout value.

Do we have any patch for this issue?

Regards
Suraj


  reply	other threads:[~2010-05-06  7:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15  5:01 [PATCH] Added support for Atheros AR300x Bluetooth Chip suraj
2010-03-24  5:27 ` suraj
2010-03-29  9:01   ` suraj
     [not found]     ` <1271673889.19858.4.camel@atheros013-desktop>
2010-04-19 18:11       ` Support " Luis R. Rodriguez
2010-03-31 10:59   ` [PATCH] Added Host level support for Atheros AR3xxx " suraj
2010-04-19 23:53 ` [PATCH] Added support for Atheros AR300x " Gustavo F. Padovan
2010-04-20 10:20 ` [PATCH v3] " suraj
2010-04-20 15:36   ` Gustavo F. Padovan
2010-04-20 17:34   ` Luis R. Rodriguez
2010-04-21  4:21     ` Suraj Sumangala
2010-04-21 10:22   ` [PATCH v4] Add support for the " suraj
2010-04-21 17:30     ` Luis R. Rodriguez
2010-04-22  6:10     ` Gustavo F. Padovan
2010-04-22  6:54       ` Suraj Sumangala
2010-04-22  8:59         ` Gustavo F. Padovan
2010-04-22  9:10     ` [PATCH v5] " suraj
2010-04-26 11:00       ` suraj
2010-04-27  6:19         ` [PATCH] New Firmware for Atheros bluetooth chipset AR3011 suraj
2010-04-27  8:28           ` [PATCH] patch to request new firmware for AR3011 Chip suraj
2010-04-27 15:55             ` Luis R. Rodriguez
2010-05-11  9:04             ` [PATCH v2] ath3k: add support for new firmware suraj
2010-05-05 12:33         ` [PATCH v5] Add support for the Atheros AR300x Bluetooth Chip suraj
2010-05-06  7:45           ` suraj [this message]
2010-05-20 16:02             ` buffer starvation with multiple ACL link Marcel Holtmann
2010-05-10 20:12           ` [PATCH v5] Add support for the Atheros AR300x Bluetooth Chip Luis R. Rodriguez
2010-05-11  8:29           ` suraj
2010-05-18 11:39             ` suraj
2010-05-12 13:47       ` [PATCH v3] hciattach application support for " suraj
2010-05-20 13:37         ` suraj
2010-05-20 16:00         ` Marcel Holtmann
2010-05-21  5:01           ` Suraj Sumangala
2010-05-21  7:34             ` Marcel Holtmann
2010-05-20 16:09       ` [PATCH v5] Add support for the " 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=1273131932.2229.9.camel@atheros013-desktop \
    --to=suraj@atheros.com \
    --cc=Jothikumar.Mothilal@Atheros.com \
    --cc=Luis.Rodriguez@Atheros.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