Hi,
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,
When channel context is enabled, we could be
stopping/awakening an incorrect queue.
Signed-off-by: Borja Salazar
---
drivers/net/wireless/ath/ath9k/xmit.c | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git
Hi,
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,
Borja Salazar 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
On 13 November 2015 at 11:45, Borja Salazar wrote:
> Hi,
>
> 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
Send again as txt.
On 13 November 2015 at 12:17, Janusz Dziedzic wrote:
>
>
>
> On 13 November 2015 at 11:45, Borja Salazar wrote:
>>
>> Hi,
>>
>> Let me explain the patch more thoroughly. We are testing MCC and we've found
>> some issues with