public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
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 17:52:04 +0300	[thread overview]
Message-ID: <20120418145202.GH19228@aemeltch-MOBL1> (raw)
In-Reply-To: <4F8ED1D0.1070401@sipsolutions.net>

Hi Johannes,

On Wed, Apr 18, 2012 at 07:38:08AM -0700, Johannes Berg wrote:
> On 4/18/2012 5:15 AM, Andrei Emeltchenko wrote:
> >>It's never in your best interest to run one supplicant per virtual
> >>interface, you want to run one per piece of hardware so it can
> >>coordinate between virtual interfaces.
> >
> >Do I understand it right that virtual interfaces are like separate devices from
> >user point of view? If I create virtual interface and assign MAC I can
> >transfer data through it without affecting other interfaces? Then
> >wpa_supplicant does not need to know about it at all.
> 
> 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?

> 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?

Best regards 
Andrei Emeltchenko 

  reply	other threads:[~2012-04-18 14:52 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 [this message]
2012-04-18 15:09                     ` Johannes Berg
2012-04-18 15:39                       ` Mat Martineau
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=20120418145202.GH19228@aemeltch-MOBL1 \
    --to=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