From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/3] ath10k: remove unnecessary warning for probe response drops
Date: Fri, 01 Apr 2016 10:43:38 +0530 [thread overview]
Message-ID: <43fd44912f230a28f0f49e303c0078f5@codeaurora.org> (raw)
In-Reply-To: <56FD5716.6030406@candelatech.com>
On 2016-03-31 22:27, Ben Greear wrote:
> On 03/30/2016 08:42 AM, Rajkumar Manoharan wrote:
>> qca99x0 and qca4019 solutions limit probe responses transmissions.
>> Logging warning message for each probe response drop is flooding
>> kernel log unnecessary with " failed to increase tx mgmt pending
>> count: -16, dropping". Hence reducing log level to debug.
>
> Is there any realistic way to see this message if we are not running
> many vAP on one radio?
>
As of now this message can be seen only with qca99x0 which has 24 as
max_probe_resp_desc_thres. Only possible way in single vAP is that in
congested environment when DUT is receiving probe requests more
frequently.
> I guess many probe requests or other management frames could also
> cause this problem?
>
Exactly.
-Rajkumar
next prev parent reply other threads:[~2016-04-01 5:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:42 [PATCH 1/3] ath10k: fix calibration init sequence of qca99x0 Rajkumar Manoharan
2016-03-30 15:42 ` [PATCH 2/3] ath10k: remove unnecessary warning for probe response drops Rajkumar Manoharan
2016-03-31 16:57 ` Ben Greear
2016-04-01 5:13 ` Rajkumar Manoharan [this message]
2016-03-30 15:42 ` [PATCH 3/3] ath10k: fix unconditional num_mpdus_ready subtraction Rajkumar Manoharan
2016-03-31 18:52 ` Ben Greear
2016-04-01 5:19 ` Rajkumar Manoharan
2016-04-05 12:46 ` Valo, Kalle
2016-04-05 12:48 ` Valo, Kalle
2016-04-05 13:34 ` Rajkumar Manoharan
2016-04-05 12:40 ` [PATCH 1/3] ath10k: fix calibration init sequence of qca99x0 Valo, Kalle
2016-04-05 13:32 ` 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=43fd44912f230a28f0f49e303c0078f5@codeaurora.org \
--to=rmanohar@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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 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).