From: Kalle Valo <kvalo@codeaurora.org>
To: Borja Salazar <borja.salazar@fon.com>
Cc: linux-wireless@vger.kernel.org, janusz.dziedzic@tieto.com,
sujith@msujith.org, ath9k-devel@lists.ath9k.org,
ath9k-devel@qca.qualcomm.com
Subject: Re: [PATCH v2] ath9k: incorrect queue may be stopped/awaken
Date: Fri, 13 Nov 2015 13:37:18 +0200 [thread overview]
Message-ID: <8737wa2kr5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CADqurOFRewt0OTU_HSCozBfmQBy53Q2DBs2vKkfw29O+pZeR7w@mail.gmail.com> (Borja Salazar's message of "Fri, 13 Nov 2015 11:49:13 +0100")
Borja Salazar <borja.salazar@fon.com> writes:
> Let me explain the patch more thoroughly. We are testing MCC and we've
> found some issues with the queues handlers, the main problem is that
> when we transmit a multicast/broadcast frame, where hw_queue is 8
> (CAB), we check queue status, which is 2(q), and if it is full and we
> have to stop it, we end stopping the wrong queue, 8, which is not
> full. From this point onwards stations are unable to connect to the
> AP.
This information should be in the commit log.
--
Kalle Valo
next prev parent reply other threads:[~2015-11-13 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 17:37 [PATCH] ath9k: incorrect queue may be stopped/awaken Borja Salazar
2015-11-12 19:57 ` Kalle Valo
2015-11-13 6:31 ` Janusz Dziedzic
2015-11-13 10:33 ` [PATCH v2] " Borja Salazar
2015-11-13 10:49 ` Borja Salazar
2015-11-13 11:37 ` Kalle Valo [this message]
[not found] ` <CADqurOGEoZ15BtcqLwQGXLoBJLUCcd6ciypuYBzVjJb7MAHYng@mail.gmail.com>
[not found] ` <CALhHN=qB-Hmr60CLyS-eV_Vx1bWL5YLP2VQ0ipV5Okphyd-OiA@mail.gmail.com>
2015-11-13 11:19 ` Janusz Dziedzic
2015-11-13 11:27 ` Borja Salazar
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=8737wa2kr5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=borja.salazar@fon.com \
--cc=janusz.dziedzic@tieto.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.org \
/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).