I agree with Stuart that there is no reason for shared lines in the first place. It seems like a design flaw to have a common queue that congests in a way that impacts the one transmit unit as the atomic forwarding plane unit.  The goal of virtual output queueing is to eliminate head of line blocking, every egress transmit unit gets its own cashier with no competition.  The VOQ queue depths should support one transmit unit and any jitter through the switching subsystem - jitter for the case of non-bloat and where a faster VOQ service rate can drain the VOQ.  If the VOQ can't be drained per a faster service rate, then it's just one transmit unit as the queue is now just a standing queue w/delay and no benefit.

Many network engineers typically, though incorrectly, perceive a transmit unit as one ethernet packet. With WiFi it's one Mu transmission or one Su transmission, with aggregation(s), which is a lot more than one ethernet packet but it depends on things like MCS, spatial stream powers, Mu peers, etc. and is variable. Some data center designs have optimized the forwarding plane for flow completion times so their equivalent transmit unit is a mouse flow.

I perceive applying AQM to shared queue congestion as a mitigation technique to a poorly designed forwarding plane. The hope is that transistor engineers don't do this and "design out the lines" from the beginning. Better switching engineering vs queue management applied afterwards as a mitigation technique.

Bob