From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend@broadcom.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Piotr Haber <phaber@broadcom.com>
Subject: Re: [PATCH 1/2] [RFC] cfg80211: configuration of Bluetooth coexistence mode
Date: Sun, 24 Feb 2013 18:28:06 +0100 [thread overview]
Message-ID: <1361726886.8129.9.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <A47087626F2942499CF47E79803E771E0431BD3C@SJEXCHMB13.corp.ad.broadcom.com>
On Sat, 2013-02-23 at 17:47 +0000, Arend Van Spriel wrote:
> On Saturday, February 23, 2013 1:30 AM Adrian Chadd wrote:
> >
> > ... why not tag such traffic with a higher QOS priority and then have
> > the BT coex module snoop thaT?
> >
>
> In the driver we could inspect each sk_buff and boost priority of any
> BOOTP packets so that it will end up in the AC_VO fifo and have
> hardware coexistence handle it further. I consider that more a
> pragmatic fix, which is not always the worst thing to go for.
Well, I don't really think that's the best idea. Sniffing the protocol
is clumsy at best.
> However, I would prefer a solution is which user-space, ie. dhcp
> client can control the priority and/or BT coexistence.
It's not just BT coex btw, with multi-channel support it might also be
interesting to not switch channels while DHCP is going on, for example.
johannes
next prev parent reply other threads:[~2013-02-24 17:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 16:59 [PATCH 1/2] [RFC] cfg80211: configuration of Bluetooth coexistence mode Arend Van Spriel
2013-02-22 20:28 ` Johannes Berg
2013-02-23 0:30 ` Adrian Chadd
2013-02-23 17:47 ` Arend Van Spriel
2013-02-24 9:12 ` Emmanuel Grumbach
2013-02-24 17:28 ` Johannes Berg [this message]
2013-02-25 5:08 ` Adrian Chadd
2013-02-25 5:54 ` Felix Fietkau
2013-02-25 10:11 ` Arend van Spriel
2013-02-25 10:25 ` Johannes Berg
2013-02-25 13:07 ` Felix Fietkau
2013-02-27 10:27 ` Dan Williams
2013-02-27 17:44 ` Arend van Spriel
2013-02-28 11:53 ` Piotr Haber
2013-02-27 18:45 ` Johannes Berg
2013-02-27 17:21 ` Arend van Spriel
-- strict thread matches above, loose matches on Subject: below --
2013-02-22 9:08 [RFC 0/2] control Bluetooth coexistence Piotr Haber
2013-02-22 9:08 ` [PATCH 1/2] [RFC] cfg80211: configuration of Bluetooth coexistence mode Piotr Haber
2013-02-22 11:52 ` Johannes Berg
2013-02-22 13:32 ` Piotr Haber
2013-02-22 14:07 ` Johannes Berg
2013-02-22 14:59 ` Piotr Haber
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=1361726886.8129.9.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=adrian@freebsd.org \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=phaber@broadcom.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).