All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org,
	David Spinadel <david.spinadel@intel.com>,
	Luca Coelho <luciano.coelho@intel.com>
Subject: Re: [PATCH 2/2] iwlwifi: mvm: Avoid deffering non bufferable frames
Date: Tue, 29 Aug 2017 11:22:41 +0300	[thread overview]
Message-ID: <87efruvl4e.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20170825082730.31388-3-luca@coelho.fi> (Luca Coelho's message of "Fri, 25 Aug 2017 11:27:30 +0300")

Luca Coelho <luca@coelho.fi> writes:

> From: David Spinadel <david.spinadel@intel.com>
>
> Use bcast station for all non bufferable frames on AP and AD-HOC.
>
> The host is no longer aware of STAs PS status because of buffer
> station offload, so we can't rely on mac80211 to toggle on
> IEEE80211_TX_CTL_NO_PS_BUFFER bit.
>
> A possible issue with buffering such frames, beside the obvious spec
> violation, is when a station disconnects while in PS but the AP isn't
> aware of that. In such scenarios the AP won't be able to send probe
> responses or auth frames so the STA won't be able to reconnect and
> the AP will have a queue hang.
>
> Fixes: 3e56eadfb6a1 ("iwlwifi: mvm: implement AP/GO uAPSD support")
> Signed-off-by: David Spinadel <david.spinadel@intel.com>
> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>

"deffering"? Should it be deferring?

-- 
Kalle Valo

  reply	other threads:[~2017-08-29  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25  8:27 [PATCH 0/2] iwlwifi: updates intended for v4.14 2017-08-25 Luca Coelho
2017-08-25  8:27 ` [PATCH 1/2] iwlwifi: fix long debug print Luca Coelho
2017-08-31 21:57   ` Joe Perches
2017-09-01  5:37     ` Luca Coelho
2017-09-01  6:15       ` Joe Perches
2017-09-01  8:15         ` Kalle Valo
2017-09-01  8:21           ` Joe Perches
2017-08-25  8:27 ` [PATCH 2/2] iwlwifi: mvm: Avoid deffering non bufferable frames Luca Coelho
2017-08-29  8:22   ` Kalle Valo [this message]
2017-08-30  7:32     ` Luca Coelho

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=87efruvl4e.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=david.spinadel@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@coelho.fi \
    --cc=luciano.coelho@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 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.