From: Catalin Drula <catalin.drula@imag.fr>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: Host to Host Controller flow control
Date: Fri, 25 Mar 2005 09:11:23 +0000 (UTC) [thread overview]
Message-ID: <loom.20050325T100311-440@post.gmane.org> (raw)
In-Reply-To: loom.20050324T175954-608@post.gmane.org
Catalin Drula <catalin.drula <at> imag.fr> writes:
> I wanted to take a shot at implementing host-to-controller flow control for
> Bluez. Before I start, it'd be great to have your thoughts on this.
Hi Marcel,
I've been looking over the code in hci_core.c and hci_event.c, in particular,
hci_tx_task, hci_sched_acl, hci_sched_sco, hci_low_sent and
hci_num_comp_pkts_evt.
It seems like we're already doing host to host controller flow control,
as far as I could tell. At the very least, we're correctly keeping track
of the number of free slots in the controller's buffers and we're never
overflowing it. Also hci_low_sent always selects the connection with the
most completed packets so there seems to be some balancing done there.
Could you point out what is missing (the reason this item is on the TODO list)?
Thanks,
Catalin
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-25 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 17:04 [Bluez-devel] Host to Host Controller flow control Catalin Drula
2005-03-25 9:11 ` Catalin Drula [this message]
2005-03-25 11:48 ` [Bluez-devel] " Marcel Holtmann
2005-03-25 12:01 ` Catalin Drula
2005-03-25 12:27 ` 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=loom.20050325T100311-440@post.gmane.org \
--to=catalin.drula@imag.fr \
--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