From: James Prestwood <james.prestwood@linux.intel.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mac80211_hwsim: allow setting iftype support
Date: Wed, 17 Oct 2018 14:05:28 -0700 [thread overview]
Message-ID: <db2eb355abb871a97f5d342d1827e72dfa351e4d.camel@linux.intel.com> (raw)
In-Reply-To: <59ef2a794c49a6afdb5606f17b3cdc7c44594498.camel@sipsolutions.net>
On Wed, 2018-10-17 at 22:58 +0200, Johannes Berg wrote:
> On Wed, 2018-10-17 at 14:00 -0700, James Prestwood wrote:
> >
> > > That makes me wonder if you'd also want to support limiting the #
> > > of
> > > interfaces/channels to mimic another device?
> >
> > Yeah it seems like it would be pretty easy to add that on top of
> > this
> > change, although I don't really see us actually using it.
>
> Sure, fair enough.
>
> > I can add it,
> > but my only concern is I would not test it up to the same level I
> > tested iftype/ciphers.
>
> If you don't really want to use it, then I don't think you need to
> add
> it. I was just wondering if it made a difference.
>
> > Maybe this is also because I am not entirely
> > sure what num_different_channels is doing. Is this only relevant
> > when
> > multiple interfaces exist on a radio? Like setting how many
> > channels
> > can be use simultaneously?
>
> Correct. "Simultaneously" is a bit of an overstatement, typically
> today
> it's implemented by TDM - if you have two interfaces with a
> connection
> to an AP each, but on different channels, each interface would just
> tell
> its AP that it's going to sleep, but instead hop to the other channel
> and tell that AP that it woke up... etc.
Ah ok, that makes sense. Ok, well I can fixup that typo, as well as
reordering the use_chanctx stuff I mentioned. Unless there was anything
else? If not I can submit v3.
>
> johannes
>
next prev parent reply other threads:[~2018-10-17 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 19:33 [PATCH v2 0/2] Configuring iftype/cipher support James Prestwood
2018-10-17 19:33 ` [PATCH v2 1/2] mac80211_hwsim: allow setting iftype support James Prestwood
2018-10-17 19:43 ` James Prestwood
2018-10-17 19:53 ` Johannes Berg
2018-10-17 21:00 ` James Prestwood
2018-10-17 20:58 ` Johannes Berg
2018-10-17 21:05 ` James Prestwood [this message]
2018-10-17 21:08 ` Johannes Berg
2018-10-17 21:15 ` James Prestwood
2018-10-17 19:33 ` [PATCH v2 2/2] mac80211_hwsim: allow configurable cipher types James Prestwood
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=db2eb355abb871a97f5d342d1827e72dfa351e4d.camel@linux.intel.com \
--to=james.prestwood@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).