From: Stanislaw Gruszka <sgruszka@redhat.com>
To: 李朝明 <chaoming_li@realsil.com.cn>
Cc: "'Larry Finger'" <Larry.Finger@lwfinger.net>,
"'John W Linville'" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
'冯春燕' <amyfcy_feng@realsil.com.cn>,
'熊光安' <guangan_xiong@realsil.com.cn>
Subject: Re: about Mac80211 scan issue
Date: Wed, 9 Feb 2011 11:54:06 +0100 [thread overview]
Message-ID: <20110209105405.GB5528@redhat.com> (raw)
In-Reply-To: <B84A4806C46340989E2A6AD2EB663300@realsil.com.cn>
On Wed, Feb 09, 2011 at 09:58:46AM +0800, 李朝明 wrote:
> recently, I found some issues on mac80211 scan about null packet.
>
> Before we switch channel in scanning, we will send null packet to AP
> to indicate that we will sleep.
> but at the same time there maybe lots of packets in HW tx buffer
> witch are all ready to tx but with out
> power save flag set to 1. if we send this null packet after these
> tx buffer packets in a low priority,
We have ieee80211_ops->flush() method to send all pending tx frames from
hw before sending null frame. I see rtlwifi does not have it.
> this will
> cause follwing null packets fail because follwing check in
> __ieee80211_tx:
> if (local->queue_stop_reasons[q] ||
> (!txpending && !skb_queue_empty(&local->pending[q])))
> ret = IEEE80211_TX_PENDING;
>
> But if we send these null before there tx buffer packets packets in
> a high priority, these packets will
> be send after this null before switch channel. and switch channel
> will cause RX packet from AP fail abruptly,
> this abruptly fail will cause DELETE BA for some AP like Belkin-8233
> 11N mode or dis-associate by some AP like Dir855 5G 11N mode
> when we to test Throughput use chariot
>
> And I found that after power save null packet have been sent, there
> are lots packet send to driver from mac80211,
> should we stop all queues after we send power save null packet and
> recover all queues after we send awake null packet.
>
> So, I don't kown if it's a mac80211's issue, Could you give some
> help?
I'm not sure if I understand problem you described. Anyway, maybe is
enaugh to implement ->flush() in rtlwifi to solve the problem?
Stanislaw
next prev parent reply other threads:[~2011-02-09 10:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 18:44 [PATCH 2/6] rtlwifi: Add usb driver Larry Finger
2011-02-07 15:07 ` Stanislaw Gruszka
2011-02-07 15:12 ` Stanislaw Gruszka
2011-02-09 1:58 ` about Mac80211 scan issue 李朝明
2011-02-09 10:54 ` Stanislaw Gruszka [this message]
[not found] ` <B8DE8263FD784AC082CFDB7E9269BAEA@realsil.com.cn>
2011-02-10 7:41 ` 答复: " Stanislaw Gruszka
[not found] ` <39A39FA0AD1A481480DE0BD469AAA79E@realsil.com.cn>
2011-02-10 9:50 ` 答复: " Stanislaw Gruszka
[not found] ` <86D43C3FD69641C38E7144E721BCC5A6@realsil.com.cn>
2011-02-10 11:37 ` 答复: 答复: 答复: about Mac80211scan issue Stanislaw Gruszka
2011-02-11 2:26 ` [RFC] mac80211: cisco 1252 HT bw20, sta->ht_cap.cap bw is wrong 李朝明
2011-02-11 10:22 ` Stanislaw Gruszka
2011-02-12 3:32 ` [RFC] mac80211: mac80211's null packet issue 李朝明
2011-02-14 10:16 ` Johannes Berg
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=20110209105405.GB5528@redhat.com \
--to=sgruszka@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=amyfcy_feng@realsil.com.cn \
--cc=chaoming_li@realsil.com.cn \
--cc=guangan_xiong@realsil.com.cn \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).