From: Mat Martineau <mathewm@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>,
Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [RFCv1] mac80211: Adds Software / Virtual AMP 80211
Date: Wed, 18 Apr 2012 08:39:31 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1204180818190.25494@mathewm-linux> (raw)
In-Reply-To: <4F8ED913.4040807@sipsolutions.net>
Andrei and Johannes -
On Wed, 18 Apr 2012, Johannes Berg wrote:
> Hi Andrei,
>
>>> No, this is incorrect. If one device wants to connect on one
>>> channel, the other typically has to use the same channel. If one
>>> device wants to scan, the other will be affected. Some hardware may
>>> support switching around between two channels, but might also
>>> support more than 2 virtual interfaces, so again they won't be
>>> independent.
>>
>> BTW: which devices can switch channels?
>
> None today, I'm working on it.
>
>>> Therefore, you need something managing all this concurrency. This is
>>> in a small part the driver which will enforce restrictions (it will
>>> reject new impossible things), but mostly the supplicant which can
>>> make policy decisions about which usage should win.
>>
>> This doesn't sound like a rocket science to me. IMO this might be done in
>> drivers. Those drivers which can switch channels why do they need
>> wpa_supplicant involved making this decision?
>
> I don't think you understand.
>
> Say our device can do 3 virtual interfaces, on 2 channels. Then if the user
> is connected to some managed network (say office network), one interface &
> channel is used up. Now the user has AMP running, another channel might be
> used up. Now the user wants to do P2P negotiation. Now the supplicant, which
> is doing the negotiation, needs to know that it can negotiate only one of
> those two channels, not any other. Or maybe P2P should win, then it might
> disconnect the AMP or the managed connection. But all those are policy
> decisions, so the driver can't really handle them.
I concur with Johannes...
All of the AMP PALs I've seen are restricted to using the current
wireless channel if a wireless interface is active. The consequence
is that if you have two BT3.0+HS devices, and their wireless
interfaces are associated with different APs on different channels,
then they are unable to use AMP.
Trying to manage two active channels with a single-radio wireless
devices is non-trivial -- there may be simultaneous beacons on
different channels, for example. I suppose it could be a different
situation when a wireless device has independent radios for 2.4GHz and
5GHz bands, but there's still a need to make decisions about which
channel(s) to use and how they are to be shared.
--
Mat Martineau
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2012-04-18 15:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 12:11 [RFCv1] Draft Software/Virtual AMP80211 Andrei Emeltchenko
2012-04-10 12:11 ` [RFCv1] mac80211: Adds Software / Virtual AMP 80211 Andrei Emeltchenko
2012-04-10 12:26 ` Julian Calaby
2012-04-10 12:47 ` Andrei Emeltchenko
2012-04-10 16:39 ` Johannes Berg
2012-04-10 21:17 ` Marcel Holtmann
2012-04-10 21:20 ` Johannes Berg
2012-04-10 21:24 ` Johannes Berg
2012-04-11 7:11 ` Andrei Emeltchenko
2012-04-18 2:03 ` Johannes Berg
2012-04-18 12:15 ` Andrei Emeltchenko
2012-04-18 14:38 ` Johannes Berg
2012-04-18 14:52 ` Andrei Emeltchenko
2012-04-18 15:09 ` Johannes Berg
2012-04-18 15:39 ` Mat Martineau [this message]
2012-04-19 6:36 ` Andrei Emeltchenko
2012-04-19 13:28 ` Johannes Berg
2012-04-19 13:39 ` Andrei Emeltchenko
2012-04-19 14:21 ` Johannes Berg
2012-04-10 21:29 ` Marcel Holtmann
2012-04-11 7:05 ` Andrei Emeltchenko
2012-04-18 2:07 ` Johannes Berg
2012-04-18 11:20 ` Andrei Emeltchenko
2012-04-18 11:51 ` Marcel Holtmann
2012-04-18 12:10 ` Andrei Emeltchenko
2012-04-18 12:15 ` Marcel Holtmann
2012-04-18 12:33 ` Andrei Emeltchenko
2012-04-18 13:11 ` Marcel Holtmann
2012-04-18 13:22 ` Andrei Emeltchenko
2012-04-18 14:29 ` Marcel Holtmann
2012-04-18 15:02 ` Andrei Emeltchenko
2012-04-18 14:34 ` Johannes Berg
2012-04-18 14:56 ` Marcel Holtmann
2012-04-18 14:30 ` Johannes Berg
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=alpine.DEB.2.02.1204180818190.25494@mathewm-linux \
--to=mathewm@codeaurora.org \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
/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