From: Ben Greear <greearb@candelatech.com>
To: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, rmanohar@codeaurora.org
Subject: Re: [PATCH] ath10k: move mgmt descriptor limit handle under mgmt_tx
Date: Sat, 05 Mar 2016 06:30:38 -0800 [thread overview]
Message-ID: <56DAED8E.6020407@candelatech.com> (raw)
In-Reply-To: <1457187017-12913-1-git-send-email-rmanohar@qti.qualcomm.com>
On 03/05/2016 06:10 AM, Rajkumar Manoharan wrote:
> Firmware reserves few descriptors for management frames transmission.
> In 16 MBSSID scenario, these slots will be easy exhausted due to frequent
> probe responses. So for 10.4 based solutions, probe responses are limited
> by a threshold (24).
Do you mean probe requests or probe responses?
A single hardware scan request with lots of ssids in it will utilize all
firmware tx management frames (which is 5, it seems). In my testing, the
firmware would just never send probe requests for the rest of the ssids
because the firmware scan state machine logic is broken.
If you really do mean responses, then it sounds like it would be better to
use the normal RX path for mgt frames in the firmware...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, rmanohar@codeaurora.org
Subject: Re: [PATCH] ath10k: move mgmt descriptor limit handle under mgmt_tx
Date: Sat, 05 Mar 2016 06:30:38 -0800 [thread overview]
Message-ID: <56DAED8E.6020407@candelatech.com> (raw)
In-Reply-To: <1457187017-12913-1-git-send-email-rmanohar@qti.qualcomm.com>
On 03/05/2016 06:10 AM, Rajkumar Manoharan wrote:
> Firmware reserves few descriptors for management frames transmission.
> In 16 MBSSID scenario, these slots will be easy exhausted due to frequent
> probe responses. So for 10.4 based solutions, probe responses are limited
> by a threshold (24).
Do you mean probe requests or probe responses?
A single hardware scan request with lots of ssids in it will utilize all
firmware tx management frames (which is 5, it seems). In my testing, the
firmware would just never send probe requests for the rest of the ssids
because the firmware scan state machine logic is broken.
If you really do mean responses, then it sounds like it would be better to
use the normal RX path for mgt frames in the firmware...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2016-03-05 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 14:10 [PATCH] ath10k: move mgmt descriptor limit handle under mgmt_tx Rajkumar Manoharan
2016-03-05 14:10 ` Rajkumar Manoharan
2016-03-05 14:30 ` Ben Greear [this message]
2016-03-05 14:30 ` Ben Greear
2016-03-06 4:00 ` Rajkumar Manoharan
2016-03-06 4:00 ` Rajkumar Manoharan
2016-03-06 4:11 ` Ben Greear
2016-03-06 4:11 ` Ben Greear
2016-03-06 6:26 ` Rajkumar Manoharan
2016-03-06 6:26 ` Rajkumar Manoharan
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=56DAED8E.6020407@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rmanohar@codeaurora.org \
--cc=rmanohar@qti.qualcomm.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.