All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: use full power if off-channel
Date: Mon, 09 Jul 2012 09:02:37 -0700	[thread overview]
Message-ID: <4FFB009D.7080400@candelatech.com> (raw)
In-Reply-To: <1341845721.4455.50.camel@jlt3.sipsolutions.net>

On 07/09/2012 07:55 AM, Johannes Berg wrote:
> On Mon, 2012-07-09 at 07:50 -0700, Ben Greear wrote:
>> On 07/09/2012 01:29 AM, Johannes Berg wrote:
>>> On Sun, 2012-07-08 at 07:34 -0700, Ben Greear wrote:
>>>> On 07/08/2012 02:35 AM, Johannes Berg wrote:
>>>>> From: Johannes Berg <johannes.berg@intel.com>
>>>>>
>>>>> Instead of using full power when scanning, use
>>>>> full power when off-channel. This is different
>>>>> since off-channel can be remain-on-channel.
>>>>
>>>> What if we are scanning on our current channel?  Shouldn't
>>>> it be full-power then as well?
>>>
>>> Arguable. If we're on the channel that the AP explicitly told us to use
>>> less power on, and we're not stopping normal traffic, then I'm not sure
>>> we should.
>>
>> Well, if you are scanning, you might be wanting to find other APs that
>> perhaps require full power to reach, so it seems to me it should scan
>> at full power...
>
> Yes, but you're not supposed to send the data packets at the higher
> power. So unless you have per-packet power control you'd be breaking
> your TPC implementation (which is regulatory relevant) if you do
> on-channel scan.
>
> I suppose the other option would be to skip the optimisation in that
> case, but ...

I guess I'd rather keep the scan-on-channel optimization and just tx
at lower power.  Another thing..with your change, we can skip a hardware
config at the start of scan-on-channel since it was only there to configure
the tx power anyway...

In general, I'd like the ability to choose the tx power on a per-packet
basis so that one virtual station could tx at a different power-setting
than another..but I've no time to work on that now, and I'm not sure hardware
would support that kind of thing anyway.

Thanks,
Ben

>
> johannes
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com



      reply	other threads:[~2012-07-09 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-08  9:35 [PATCH] mac80211: use full power if off-channel Johannes Berg
2012-07-08 14:34 ` Ben Greear
2012-07-09  8:29   ` Johannes Berg
2012-07-09 14:50     ` Ben Greear
2012-07-09 14:55       ` Johannes Berg
2012-07-09 16:02         ` Ben Greear [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=4FFB009D.7080400@candelatech.com \
    --to=greearb@candelatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.