From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/4] Bluetooth: prioritizing data over HCI
Date: Wed, 02 Nov 2011 15:22:31 +0100 [thread overview]
Message-ID: <1320243753.15441.282.camel@aeonflux> (raw)
In-Reply-To: <1320241924-2300-1-git-send-email-luiz.dentz@gmail.com>
Hi Luiz,
> This implement priority based scheduler using skbuffer priority set via
> SO_PRIORITY socket option.
>
> It introduces hci_chan_hash (list of HCI Channel/hci_chan) per connection,
> each item in this list refer to a L2CAP connection and it is used to
> queue the data for transmission.
>
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> ---
> include/net/bluetooth/hci_core.h | 43 +++++++++++-
> include/net/bluetooth/l2cap.h | 1 +
> net/bluetooth/hci_conn.c | 53 ++++++++++++++
> net/bluetooth/hci_core.c | 143 ++++++++++++++++++++++++++++++++------
> net/bluetooth/l2cap_core.c | 63 +++++++++--------
> net/bluetooth/smp.c | 3 +-
> 6 files changed, 251 insertions(+), 55 deletions(-)
I looked through all 4 patches and it seems fine to me. Lets get this
merged and take it for a spin.
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
prev parent reply other threads:[~2011-11-02 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 13:52 [PATCH 1/4] Bluetooth: prioritizing data over HCI Luiz Augusto von Dentz
2011-11-02 13:52 ` [PATCH 2/4] Bluetooth: handle priority change within quote Luiz Augusto von Dentz
2011-11-02 13:52 ` [PATCH 3/4] Bluetooth: recalculate priorities when channels are starving Luiz Augusto von Dentz
2011-11-02 13:52 ` [PATCH 4/4] Bluetooth: use buffer priority to mark URB_ISO_ASAP flag Luiz Augusto von Dentz
2011-11-03 14:25 ` Gustavo Padovan
2011-11-30 17:24 ` Vinicius Costa Gomes
2011-12-01 7:23 ` Luiz Augusto von Dentz
2011-12-02 12:25 ` Gustavo Padovan
2011-12-22 1:07 ` Vinicius Costa Gomes
2011-11-02 14:22 ` Marcel Holtmann [this message]
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=1320243753.15441.282.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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).