linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: linux-wireless@vger.kernel.org,
	Matti Gottlieb <matti.gottlieb@intel.com>
Subject: Re: [PATCH] mac80211: While associated, force off channel transmission for action frames
Date: Fri, 24 Apr 2015 12:28:03 +0200	[thread overview]
Message-ID: <1429871283.1852.28.camel@sipsolutions.net> (raw)
In-Reply-To: <1429559654-23126-1-git-send-email-emmanuel.grumbach@intel.com>

On Mon, 2015-04-20 at 22:54 +0300, Emmanuel Grumbach wrote:
> From: Matti Gottlieb <matti.gottlieb@intel.com>
> 
> Currently while associated to an AP and sending an action frame to a
> different AP on the same channel, the action frame will be sent
> like a regular tx frame without going off channel.
> 
> When power save is enabled this can cause problems, since the device can
> go into power save and miss the response to the action frame that is sent
> by the other AP.
> 
> By forcing the frame to be transmitted off channel we avoid this issue.
> 
> Force the transmitting of the action frame to use off channel in
> case of association
> - If HW off channel is enabled
> - The user did not forbid transmitting frames off channel
> - The frame is not designated to the AP that we are associated with

Makes sense, but I reworded the commit message a bit.

If this problem crops up on non-hw-offchannel devices we should prevent
powersave there for the transition period.

johannes


      reply	other threads:[~2015-04-24 10:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 19:54 [PATCH] mac80211: While associated, force off channel transmission for action frames Emmanuel Grumbach
2015-04-24 10:28 ` 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=1429871283.1852.28.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=emmanuel.grumbach@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=matti.gottlieb@intel.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).