Skip to contentSkip to conversation

mac80211: changing number of queues in ops->start

DISCUSSION Michael Buesch 2 participants 7 messages Apr 7, 2009

lore
Share & tools
lore
#0 lore raw

I'm wondering how to implement QoS capability runtime detection in a mac80211 driver.

In b43 we don't know at ieee80211_register time whether the firmware does support QoS or not, because it's not loaded yet. (Reasons for not loading it that early are issues with builtin-b43, etc...).
So we don't know whether we are going to load opensource fw (no QoS) or proprietary fw (QoS capable).
But it seems that mac80211 requires to set hw->queues before ieee80211_register.

So what I'd need is a way to change the number of possible queues from within the ops->start handler.

Any ideas?

Signature · 1 line
Greetings, Michael.
#1 lore raw
Quoted 10 lines · Michael Buesch

I'm wondering how to implement QoS capability runtime detection in a mac80211 driver.

In b43 we don't know at ieee80211_register time whether the firmware does support QoS or not, because it's not loaded yet. (Reasons for not loading it that early are issues with builtin-b43, etc...).
So we don't know whether we are going to load opensource fw (no QoS) or proprietary fw (QoS capable).
But it seems that mac80211 requires to set hw->queues before ieee80211_register.

Quoted 2 lines

So what I'd need is a way to change the number of possible queues from within the ops->start handler.

Well, I suppose you could register with the max and later reduce and stop the remaining queues you're not using... Or not stop them and drop packets on them. That's somewhat fragile, gives people who look at tc a wrong idea, and I can't imagine supporting it, but it should work.

johannes

#2 lore raw
Quoted 11 lines · On Tuesday 07 April 2009 21:29:27 Johannes Berg wrote:
Quoted 10 lines · Michael Buesch

I'm wondering how to implement QoS capability runtime detection in a mac80211 driver.

In b43 we don't know at ieee80211_register time whether the firmware does support QoS or not, because it's not loaded yet. (Reasons for not loading it that early are issues with builtin-b43, etc...).
So we don't know whether we are going to load opensource fw (no QoS) or proprietary fw (QoS capable).
But it seems that mac80211 requires to set hw->queues before ieee80211_register.

Quoted 7 lines
Quoted 2 lines

So what I'd need is a way to change the number of possible queues from within the ops->start handler.

Well, I suppose you could register with the max and later reduce and stop the remaining queues you're not using... Or not stop them and drop packets on them. That's somewhat fragile, gives people who look at tc a wrong idea, and I can't imagine supporting it, but it should work.

mkay, I'll try this. thanks :)

I wonder, however, will mac80211 try to queue packets on queues that are stopped? And I think just dropping them is not an option, because this will cause breakage.

What about just queueing everything on a single queue, no matter what queue mac80211 puts the frame into? Would this cause ordering issues?
Or the other way around, is there anything that _depends_ on the higher priority queues to get sent before the higher priority queues?

Signature · 1 line
Greetings, Michael.
#3 lore raw
Quoted 7 lines · Michael Buesch
Quoted 4 lines

Well, I suppose you could register with the max and later reduce and stop the remaining queues you're not using... Or not stop them and drop packets on them. That's somewhat fragile, gives people who look at tc a wrong idea, and I can't imagine supporting it, but it should work.

mkay, I'll try this. thanks :)

Quoted 7 lines

I wonder, however, will mac80211 try to queue packets on queues that are stopped? And I think just dropping them is not an option, because this will cause breakage.

What about just queueing everything on a single queue, no matter what queue mac80211 puts the frame into? Would this cause ordering issues?
Or the other way around, is there anything that _depends_ on the higher priority queues to get sent before the higher priority queues?

mac80211 won't try to select a queue higher than hw->queues at select_queue time, so it shouldn't try to put packets onto that queue, look in wme.c.

johannes

#4 lore raw
Quoted 12 lines · On Tuesday 07 April 2009 21:37:58 Johannes Berg wrote:
Quoted 10 lines · Michael Buesch
Quoted 4 lines

Well, I suppose you could register with the max and later reduce and stop the remaining queues you're not using... Or not stop them and drop packets on them. That's somewhat fragile, gives people who look at tc a wrong idea, and I can't imagine supporting it, but it should work.

mkay, I'll try this. thanks :)

I wonder, however, will mac80211 try to queue packets on queues that are stopped? And I think just dropping them is not an option, because this will cause breakage.

Quoted 8 lines
Quoted 4 lines

What about just queueing everything on a single queue, no matter what queue mac80211 puts the frame into? Would this cause ordering issues?
Or the other way around, is there anything that _depends_ on the higher priority queues to get sent before the higher priority queues?

mac80211 won't try to select a queue higher than hw->queues at select_queue time, so it shouldn't try to put packets onto that queue, look in wme.c.

Ok I see. So you say it's OK to lower hw->queues after ieee80211_register. Should I reset hw->queues back to the value ieee80211_register was called with, before I call unregister/free? Are there resources allocated by the number of queues?

Signature · 1 line
Greetings, Michael.
#5 lore raw
Quoted 1 line · Michael Buesch

Ok I see. So you say it's OK to lower hw->queues after ieee80211_register.

Let's say it's acceptable ;)

Quoted 2 lines

Should I reset hw->queues back to the value ieee80211_register was called with, before I call unregister/free? Are there resources allocated by the number of queues?

There are resources allocated, notably the qdiscs etc. in alloc_ether_mq() or whatever it's called in register_hw(). But the networking core should keep track of those so it shouldn't matter what the value is. OTOH if it can switch back and forth the pending packets are done per queue... for example ieee80211_clear_tx_pending will be called at unregister times, so if it's possible to be up with 4 queues, and later be up with 1, you will want to unregister with 4.

johannes

#6 lore raw
Quoted 9 lines · On Tuesday 07 April 2009 21:46:29 Johannes Berg wrote:
Quoted 1 line · Michael Buesch

Ok I see. So you say it's OK to lower hw->queues after ieee80211_register.

Let's say it's acceptable ;)

Quoted 2 lines

Should I reset hw->queues back to the value ieee80211_register was called with, before I call unregister/free? Are there resources allocated by the number of queues?

Quoted 7 lines

There are resources allocated, notably the qdiscs etc. in alloc_ether_mq() or whatever it's called in register_hw(). But the networking core should keep track of those so it shouldn't matter what the value is. OTOH if it can switch back and forth the pending packets are done per queue... for example ieee80211_clear_tx_pending will be called at unregister times, so if it's possible to be up with 4 queues, and later be up with 1, you will want to unregister with 4.

Ok, sounds like a huge hack to me. :) I'll think about it.

Signature · 1 line
Greetings, Michael.