From: Gustavo Padovan <padovan@profusion.mobi>
To: Ulisses Furquim <ulisses@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Remove global mutex hci_task_lock
Date: Wed, 21 Dec 2011 02:20:20 -0200 [thread overview]
Message-ID: <20111221042020.GC2729@joana> (raw)
In-Reply-To: <1324408251-8116-1-git-send-email-ulisses@profusion.mobi>
Hi Ulisses,
* Ulisses Furquim <ulisses@profusion.mobi> [2011-12-20 17:10:51 -0200]:
> The hci_task_lock mutex (previously a lock) was supposed to protect the
> register/unregister of HCI protocols against RX/TX tasks. This will not
> be needed anymore because SCO and L2CAP will always be compiled.
>
> Moreover, with the recent move of RX/TX to workqueues per device the
> global hci_task_lock was causing starvation between different HCI
> devices.
>
> Signed-off-by: Ulisses Furquim <ulisses@profusion.mobi>
> ---
> net/bluetooth/hci_core.c | 21 +--------------------
> 1 files changed, 1 insertions(+), 20 deletions(-)
Patch has been applied, thanks.
Gustavo
prev parent reply other threads:[~2011-12-21 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 19:10 [PATCH] Bluetooth: Remove global mutex hci_task_lock Ulisses Furquim
2011-12-20 20:58 ` Marcel Holtmann
2011-12-20 21:02 ` Ulisses Furquim
2011-12-21 4:20 ` Gustavo Padovan [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=20111221042020.GC2729@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ulisses@profusion.mobi \
/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).