Erik Stromdahl wrote:
> Iterating the TX queue and thereby dequeuing all available packets in the
> queue could result in performance penalties on some SMP systems.
>
> The reason for this is most likely that the per-ac lock (active_txq_lock)
> in mac80211 will be held by the CPU iterating the
Erik Stromdahl wrote:
> Iterating the TX queue and thereby dequeuing all available packets in the
> queue could result in performance penalties on some SMP systems.
>
> The reason for this is most likely that the per-ac lock (active_txq_lock)
> in mac80211 will be held by the CPU iterating the
Erik Stromdahl writes:
> On 4/16/19 9:07 PM, Toke Høiland-Jørgensen wrote:
>> Erik Stromdahl writes:
>>
>>> On 4/1/19 1:05 PM, Toke Høiland-Jørgensen wrote:
Erik Stromdahl writes:
> Iterating the TX queue and thereby dequeuing all available packets in the
> queue could result
On 4/16/19 9:07 PM, Toke Høiland-Jørgensen wrote:
Erik Stromdahl writes:
On 4/1/19 1:05 PM, Toke Høiland-Jørgensen wrote:
Erik Stromdahl writes:
Iterating the TX queue and thereby dequeuing all available packets in the
queue could result in performance penalties on some SMP systems.
Erik Stromdahl writes:
> On 4/1/19 1:05 PM, Toke Høiland-Jørgensen wrote:
>> Erik Stromdahl writes:
>>
>>> Iterating the TX queue and thereby dequeuing all available packets in the
>>> queue could result in performance penalties on some SMP systems.
>>>
>>> The reason for this is most likely
On 4/1/19 1:05 PM, Toke Høiland-Jørgensen wrote:
Erik Stromdahl writes:
Iterating the TX queue and thereby dequeuing all available packets in the
queue could result in performance penalties on some SMP systems.
The reason for this is most likely that the per-ac lock (active_txq_lock)
in
On 2019-03-29 15:47, Erik Stromdahl wrote:
On 3/27/19 6:49 PM, Peter Oh wrote:
On 03/27/2019 09:29 AM, Erik Stromdahl wrote:
Iterating the TX queue and thereby dequeuing all available packets in
the
queue could result in performance penalties on some SMP systems.
Please share the test
Erik Stromdahl writes:
> Iterating the TX queue and thereby dequeuing all available packets in the
> queue could result in performance penalties on some SMP systems.
>
> The reason for this is most likely that the per-ac lock (active_txq_lock)
> in mac80211 will be held by the CPU iterating the
On 3/27/19 6:49 PM, Peter Oh wrote:
On 03/27/2019 09:29 AM, Erik Stromdahl wrote:
Iterating the TX queue and thereby dequeuing all available packets in the
queue could result in performance penalties on some SMP systems.
Please share the test results and numbers you've run to help others
On 03/27/2019 09:29 AM, Erik Stromdahl wrote:
> Iterating the TX queue and thereby dequeuing all available packets in the
> queue could result in performance penalties on some SMP systems.
>
Please share the test results and numbers you've run to help others
thoughts.
Thanks,
Peter
Iterating the TX queue and thereby dequeuing all available packets in the
queue could result in performance penalties on some SMP systems.
The reason for this is most likely that the per-ac lock (active_txq_lock)
in mac80211 will be held by the CPU iterating the current queue.
This will lock up
11 matches
Mail list logo
