[Make-wifi-fast] Get hardware queue length for wireless interface in linux kernel

Toke Høiland-Jørgensen toke at toke.dk
Mon May 15 13:55:04 EDT 2017


"Mohan, Nitinder" <nitinder.mohan at helsinki.fi> writes:

> Hi,
>
> I am a Ph.D. student working on a bufferbloat resistant scheduler for
> Multi-Path TCP. I was unsure of which list my question would be more
> suitable in so I am sending this in both make-wifi-fast and bloat-dev
> list.

Sounds interesting! What, exactly, is such a scheduler going to be
doing? :)

> While implementing the scheduler in linux kernel, I was unable to get
> the current number of bytes in hardware queue for wlan interface. As
> currently, linux does not employ BQL for wifi devices, I could not get
> this value from dql->num_queued defined in dynamic_queue_limits.h. I
> also tried to get queue length from Queueing discipline structure i.e.
> qdisc->qstats.qlen defined in sch_generic.h yet it still gives me a
> zero value (I am getting zero values for other parameters in qstat as
> well so I am sure it is not because the queue length never becomes
> more than 0).
>
> If you have any idea for getting queue length for wireless interfaces,
> please do reply. Any help would be highly appreciated.

There's no general interface to get the queue length for WiFi
interfaces. If you're using a driver that is using the mac80211
intermediate queues (i.e., ath9k, ath10k or mt76), there are
fq->backlock and fq->memory_usage which live inside the struct fq in
struct ieee80211_local. However, these are private state vars inside
mac80211, so not immediately accessible from other parts of the kernel.
You could add an access function to mac80211, though.

Other drivers will have their own queueing implementations, that you
probably can't get at. Some devices will even have most of their
queueing in firmware.

-Toke


More information about the Bloat-devel mailing list