From: Ajay <ajay.kv@globaledgesoft.com>
To: linux-bluetooth@vger.kernel.org
Subject: Simultaneous data transfer on ACL and BLE links
Date: Tue, 22 Jan 2013 02:34:57 +0530 [thread overview]
Message-ID: <50FDAD79.8040700@globaledgesoft.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
Hi ,
Kernel has set some restrictions in simultaneous L2cap data
transfer on BLE and ACL links on a common device .
My test scenario is as follows
Device A has both LE and ACL link with device B and C
respectively . when i start sending l2cap data on ACL link (A to B),
it work fine . But when i starts sending BLE data along with ACL data
(A to C ) , it fails with error "send failed : interrupt system call"
. when i count the LE packets that had reached upto hci layer , it
shows some 367 packets.
Later i noticed that LE data is getting queued at hci
layer and it is not scheduled properly . following piece of code
tells us the order of scheduling.. (hci_core.c)
static void hci_tx_task(unsigned long arg)
{
struct hci_dev *hdev = (struct hci_dev *) arg;
struct sk_buff *skb;
read_lock(&hci_task_lock);
BT_DBG("%s acl %d sco %d le %d", hdev->name, hdev->acl_cnt,
hdev->sco_cnt, hdev->le_cnt);
/* Schedule queues and send stuff to HCI driver */
hci_sched_acl(hdev);
hci_sched_sco(hdev);
hci_sched_esco(hdev);
hci_sched_le(hdev);
......
Here both acl and le scheduling are using same count as
reference (hdev->acl_cnt) and they have never make use of hdev->le_cnt.
please kindly go through this issue.
--
Thanks & Regards
AJAY KV
GlobalEdge software Ltd
8892753703
[-- Attachment #2: ajay_kv.vcf --]
[-- Type: text/x-vcard, Size: 74 bytes --]
begin:vcard
fn:AJAY KV
n:;AJAY
tel;cell:8892753703
version:2.1
end:vcard
reply other threads:[~2013-01-21 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50FDAD79.8040700@globaledgesoft.com \
--to=ajay.kv@globaledgesoft.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;
as well as URLs for NNTP newsgroup(s).