Return-Path: Subject: Re: [Bluez-devel] Re: Host to Host Controller flow control From: Marcel Holtmann To: BlueZ Mailing List In-Reply-To: References: Content-Type: text/plain Message-Id: <1111751283.9195.60.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 25 Mar 2005 12:48:03 +0100 Hi Catalin, > 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)? the host to host controller flow control means that we tell the chip to use flow control. This is the other way around and we don't support it at the moment, because it is easy for us to handle big packets. If you enable host to host controller flow control you need to tell the chip when you are ready to receive more packets. Regards Marcel ------------------------------------------------------- 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