From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Mahesh Palivela <maheshp@posedge.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
Stanislaw Gruszka <sgruszka@redhat.com>
Subject: Re: [RFC v3] cfg80211: VHT regulatory
Date: Fri, 28 Sep 2012 08:40:21 +0200 [thread overview]
Message-ID: <1348814421.9978.4.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6URYEr4d6ti0W7Go37x1fRM_9XD09cQXx4EJ6afhpPuXA@mail.gmail.com> (sfid-20120925_210657_912005_3BE19F7C)
On Tue, 2012-09-25 at 12:06 -0700, Luis R. Rodriguez wrote:
> > You've got to be kidding? Runtime cost of this is negligible, we only
> > execute the test when we switch channels which happens very
> > infrequently.
>
> Well considering P2P technologies slowly blooming I would disagree
> that channel changes are going to be infrequent. Then we also have
> scanning which can happen any time you move away from your AP and at a
> specific interval. Are we going to remove the capability to use each
> channel as cached value and always ask cfg80211 it we can move on?
They're still going to be infrequent, you're not going to switch
channels (in mac80211) for every other packet :-) Even if you were to do
channel switching every couple of seconds, which is really unlikely and
will kill all performance, the calculation overhead wouldn't matter.
johannes
prev parent reply other threads:[~2012-09-28 6:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 10:06 [RFC v3] cfg80211: VHT regulatory Mahesh Palivela
2012-09-13 20:41 ` Luis R. Rodriguez
2012-09-14 8:18 ` Mahesh Palivela
2012-09-17 15:34 ` Johannes Berg
2012-09-17 18:56 ` Luis R. Rodriguez
2012-09-24 10:48 ` Johannes Berg
2012-09-24 23:24 ` Luis R. Rodriguez
2012-09-25 7:16 ` Johannes Berg
2012-09-25 19:06 ` Luis R. Rodriguez
2012-09-28 3:41 ` Mahesh Palivela
2012-09-28 6:40 ` Johannes Berg [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=1348814421.9978.4.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maheshp@posedge.com \
--cc=mcgrof@do-not-panic.com \
--cc=sgruszka@redhat.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).