Skip to contentSkip to conversation

ath9k: fix tx queue selection

RFC In review Björn Smedman 4 participants 16 messages Nov 2, 2010 – Nov 3, 2010 Qualcomm Atheros ATH9K wireless driver

lore
Share & tools
lore
#0 lore raw

RFC 1/1 ath9k: fix tx queue selection

Hi all,

The following patch attempts to fix some problems with ath9k tx queue selection:

1. There was a posible mismatch between the queue selected for QoS packets (on which locking, queue start/stop and statistics where performed) and the queue actually used for TX. This is fixed by selecting the tx queue based on the TID of the 802.11 header for this type of packet.

2. Even with the above fix there was still a risk of mac80211 queue "deadlock" because the queue to stop was selected on the basis of the skb queue mapping whereas the queue to start was selected based on the hardware tx queue to mac80211 queue mapping. These may not in all situations be one and the same.

This patch is against latest wireless-testing but I've only tested it against compat-wireless-2010-10-19 with openwrt patches on top (including Luis latest pcu lock patch) and some other patches I'm working on. If you can run wireless-testing directly, please give it a spin. For me it's a big improvement in stability under high tx/rx load.

Any thoughts?

/Bj?rn

---

drivers/net/wireless/ath/ath9k/main.c +8 -3
index a133878..bbc292a 100644
@@ -1266,6 +1266,14 @@ static int ath9k_tx(struct ieee80211_hw *hw,
 		hdr->seq_ctrl |= cpu_to_le16(sc->tx.seq_no);
 	}
 
+	if (ieee80211_is_data_qos(hdr->frame_control)) {
+		u8 *qc = ieee80211_get_qos_ctl(hdr);
+		qnum = sc->tx.hwq_map[TID_TO_WME_AC(qc[0] & 0xf)];
+	} else
+		qnum = ath_get_hal_qnum(skb_get_queue_mapping(skb), sc);
+
+	txctl.txq = &sc->tx.txq[qnum];
+
 	/* Add the padding after the header if this is not already done */
 	padpos = ath9k_cmn_padpos(hdr->frame_control);
 	padsize = padpos & 3;
@@ -1276,9 +1284,6 @@ static int ath9k_tx(struct ieee80211_hw *hw,
 		memmove(skb->data, skb->data + padsize, padpos);
 	}
 
-	qnum = ath_get_hal_qnum(skb_get_queue_mapping(skb), sc);
-	txctl.txq = &sc->tx.txq[qnum];
-
 	ath_print(common, ATH_DBG_XMIT, "transmitting packet, skb: %p\n", skb);
 
 	if (ath_tx_start(hw, skb, &txctl) != 0) {
drivers/net/wireless/ath/ath9k/xmit.c +15 -9
index f7da6b2..5be9d5e 100644
@@ -2011,17 +2011,17 @@ static void ath_tx_rc_status(struct ath_buf *bf, struct ath_tx_status *ts,
 	tx_info->status.rates[tx_rateindex].count = ts->ts_longretry + 1;
 }
 
-static void ath_wake_mac80211_queue(struct ath_softc *sc, struct ath_txq *txq)
+static void ath_wake_mac80211_queue(struct ath_softc *sc, struct ath_txq *txq,
+				    int qm)
 {
-	int qnum;
+	int q = qm;
 
-	qnum = ath_get_mac80211_qnum(txq->axq_class, sc);
-	if (qnum == -1)
-		return;
+        if (q >= 4)
+                q = 0;
 
 	spin_lock_bh(&txq->axq_lock);
-	if (txq->stopped && sc->tx.pending_frames[qnum] < ATH_MAX_QDEPTH) {
-		if (ath_mac80211_start_queue(sc, qnum))
+	if (txq->stopped && sc->tx.pending_frames[q] < ATH_MAX_QDEPTH) {
+		if (ath_mac80211_start_queue(sc, qm))
 			txq->stopped = 0;
 	}
 	spin_unlock_bh(&txq->axq_lock);
@@ -2037,6 +2037,7 @@ static void ath_tx_processq(struct ath_softc *sc, struct ath_txq *txq)
 	struct ath_tx_status ts;
 	int txok;
 	int status;
+	int qm;
 
 	ath_print(common, ATH_DBG_QUEUE, "tx queue %d (%x), link %p\n",
 		  txq->axq_qnum, ath9k_hw_gettxbuf(sc->sc_ah, txq->axq_qnum),
@@ -2124,12 +2125,14 @@ static void ath_tx_processq(struct ath_softc *sc, struct ath_txq *txq)
 			ath_tx_rc_status(bf, &ts, 0, txok, true);
 		}
 
+		qm = skb_get_queue_mapping(bf->bf_mpdu);
+
 		if (bf_isampdu(bf))
 			ath_tx_complete_aggr(sc, txq, bf, &bf_head, &ts, txok);
 		else
 			ath_tx_complete_buf(sc, bf, txq, &bf_head, &ts, txok, 0);
 
-		ath_wake_mac80211_queue(sc, txq);
+		ath_wake_mac80211_queue(sc, txq, qm);
 
 		spin_lock_bh(&txq->axq_lock);
 		if (sc->sc_flags & SC_OP_TXAGGR)
@@ -2199,6 +2202,7 @@ void ath_tx_edma_tasklet(struct ath_softc *sc)
 	struct list_head bf_head;
 	int status;
 	int txok;
+	int qm;
 
 	for (;;) {
 		status = ath9k_hw_txprocdesc(ah, NULL, (void *)&txs);
@@ -2253,13 +2257,15 @@ void ath_tx_edma_tasklet(struct ath_softc *sc)
 			ath_tx_rc_status(bf, &txs, 0, txok, true);
 		}
 
+		qm = skb_get_queue_mapping(bf->bf_mpdu);
+
 		if (bf_isampdu(bf))
 			ath_tx_complete_aggr(sc, txq, bf, &bf_head, &txs, txok);
 		else
 			ath_tx_complete_buf(sc, bf, txq, &bf_head,
 					    &txs, txok, 0);
 
-		ath_wake_mac80211_queue(sc, txq);
+		ath_wake_mac80211_queue(sc, txq, qm);
 
 		spin_lock_bh(&txq->axq_lock);
 		if (!list_empty(&txq->txq_fifo_pending)) {
#1 lore raw
Quoted 9 lines · Bj?rn Smedman

Hi all,

The following patch attempts to fix some problems with ath9k tx queue selection:

1. There was a posible mismatch between the queue selected for QoS packets (on which locking, queue start/stop and statistics where performed) and the queue actually used for TX. This is fixed by selecting the tx queue based on the TID of the 802.11 header for this type of packet.

This should not be necessary. mac80211 should take care of queue selection properly for QoS frames. If it doesn't, then that is the bug that needs to be fixed...

Quoted 5 lines

2. Even with the above fix there was still a risk of mac80211 queue "deadlock" because the queue to stop was selected on the basis of the skb queue mapping whereas the queue to start was selected based on the hardware tx queue to mac80211 queue mapping. These may not in all situations be one and the same.

Instead of working around this, we need to make sure that those are always identical.

Quoted 7 lines

This patch is against latest wireless-testing but I've only tested it against compat-wireless-2010-10-19 with openwrt patches on top (including Luis latest pcu lock patch) and some other patches I'm working on. If you can run wireless-testing directly, please give it a spin. For me it's a big improvement in stability under high tx/rx load.

Any thoughts?

Let's do a thorough review of the tx path and figure out where the mismatch is actually coming from.

- Felix

#2 lore raw

RFC 1/1 ath9k: fix tx queue selection

Quoted 28 lines · Felix Fietkau
Quoted 9 lines · Bj?rn Smedman

Hi all,

The following patch attempts to fix some problems with ath9k tx queue selection:

1. There was a posible mismatch between the queue selected for QoS packets (on which locking, queue start/stop and statistics where performed) and the queue actually used for TX. This is fixed by selecting the tx queue based on the TID of the 802.11 header for this type of packet.

This should not be necessary. mac80211 should take care of queue selection properly for QoS frames. If it doesn't, then that is the bug that needs to be fixed...

Quoted 5 lines

2. Even with the above fix there was still a risk of mac80211 queue "deadlock" because the queue to stop was selected on the basis of the skb queue mapping whereas the queue to start was selected based on the hardware tx queue to mac80211 queue mapping. These may not in all situations be one and the same.

Instead of working around this, we need to make sure that those are always identical.

Quoted 6 lines

This patch is against latest wireless-testing but I've only tested it against compat-wireless-2010-10-19 with openwrt patches on top (including Luis latest pcu lock patch) and some other patches I'm working on. If you can run wireless-testing directly, please give it a spin. For me it's a big improvement in stability under high tx/rx load.

Quoted 3 lines
Quoted 1 line

Any thoughts?

Let's do a thorough review of the tx path and figure out where the mismatch is actually coming from.

Bj?rn, how about this instead? Please test if it improves the stability in your tests.

drivers/net/wireless/ath/ath9k/xmit.c +11 -15
@@ -1747,6 +1747,7 @@ int ath_tx_start(struct ieee80211_hw *hw
 		return -1;
 	}
 
+	q = ath_get_mac80211_qnum(txq->axq_class, sc);
 	r = ath_tx_setup_buffer(hw, bf, skb, txctl);
 	if (unlikely(r)) {
 		ath_print(common, ATH_DBG_FATAL, "TX mem alloc failure\n");
@@ -1756,8 +1757,8 @@ int ath_tx_start(struct ieee80211_hw *hw
 		 * we will at least have to run TX completionon one buffer
 		 * on the queue */
 		spin_lock_bh(&txq->axq_lock);
-		if (!txq->stopped && txq->axq_depth > 1) {
-			ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+		if (q >= 0 && !txq->stopped && txq->axq_depth > 1) {
+			ath_mac80211_stop_queue(sc, q);
 			txq->stopped = 1;
 		}
 		spin_unlock_bh(&txq->axq_lock);
@@ -1767,13 +1768,10 @@ int ath_tx_start(struct ieee80211_hw *hw
 		return r;
 	}
 
-	q = skb_get_queue_mapping(skb);
-	if (q >= 4)
-		q = 0;
-
 	spin_lock_bh(&txq->axq_lock);
-	if (++sc->tx.pending_frames[q] > ATH_MAX_QDEPTH && !txq->stopped) {
-		ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+	if (q >= 0 && ++sc->tx.pending_frames[q] > ATH_MAX_QDEPTH &&
+	    !txq->stopped) {
+		ath_mac80211_stop_queue(sc, q);
 		txq->stopped = 1;
 	}
 	spin_unlock_bh(&txq->axq_lock);
@@ -1841,7 +1839,8 @@ exit:
 /*****************/
 
 static void ath_tx_complete(struct ath_softc *sc, struct sk_buff *skb,
-			    struct ath_wiphy *aphy, int tx_flags)
+			    struct ath_wiphy *aphy, struct ath_txq *txq,
+			    int tx_flags)
 {
 	struct ieee80211_hw *hw = sc->hw;
 	struct ieee80211_tx_info *tx_info = IEEE80211_SKB_CB(skb);
@@ -1887,11 +1886,8 @@ static void ath_tx_complete(struct ath_s
 	if (unlikely(tx_info->pad[0] & ATH_TX_INFO_FRAME_TYPE_INTERNAL))
 		ath9k_tx_status(hw, skb);
 	else {
-		q = skb_get_queue_mapping(skb);
-		if (q >= 4)
-			q = 0;
-
-		if (--sc->tx.pending_frames[q] < 0)
+		q = ath_get_mac80211_qnum(txq->axq_class, sc);
+		if (q >= 0 && --sc->tx.pending_frames[q] < 0)
 			sc->tx.pending_frames[q] = 0;
 
 		ieee80211_tx_status(hw, skb);
@@ -1928,7 +1924,7 @@ static void ath_tx_complete_buf(struct a
 			complete(&sc->paprd_complete);
 	} else {
 		ath_debug_stat_tx(sc, txq, bf, ts);
-		ath_tx_complete(sc, skb, bf->aphy, tx_flags);
+		ath_tx_complete(sc, skb, bf->aphy, txq, tx_flags);
 	}
 	/* At this point, skb (bf->bf_mpdu) is consumed...make sure we don't
 	 * accidentally reference it later.
#3 lore raw

2010/11/2 Felix Fietkau <[email protected]>:

Quoted 6 lines

+ ? ? ? q = ath_get_mac80211_qnum(txq->axq_class, sc);
? ? ? ?r = ath_tx_setup_buffer(hw, bf, skb, txctl);
? ? ? ?if (unlikely(r)) {
? ? ? ? ? ? ? ?ath_print(common, ATH_DBG_FATAL, "TX mem alloc failure\n");

(quoted diff) +0 -0
@@ -1756,8 +1757,8 @@ int ath_tx_start(struct ieee80211_hw *hw

? ? ? ? ? ? ? ? * we will at least have to run TX completionon one buffer

Quoted 8 lines

? ? ? ? ? ? ? ? * on the queue */
? ? ? ? ? ? ? ?spin_lock_bh(&txq->axq_lock);
- ? ? ? ? ? ? ? if (!txq->stopped && txq->axq_depth > 1) {
- ? ? ? ? ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+ ? ? ? ? ? ? ? if (q >= 0 && !txq->stopped && txq->axq_depth > 1) {
+ ? ? ? ? ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, q);
? ? ? ? ? ? ? ? ? ? ? ?txq->stopped = 1;
? ? ? ? ? ? ? ?}

You cannot be sure that you are stopping the queue that the skb actually came in on here since mac80211 queues are mapped to hw queues by ath_get_hal_qnum() and that mapping is not reversible (due to the default statement):

static int ath_get_hal_qnum(u16 queue, struct ath_softc *sc)

{
        int qnum;

        switch (queue) {
        case 0:
                qnum = sc->tx.hwq_map[WME_AC_VO];
                break;
        case 1:
                qnum = sc->tx.hwq_map[WME_AC_VI];
                break;
        case 2:
                qnum = sc->tx.hwq_map[WME_AC_BE];
                break;
        case 3:
                qnum = sc->tx.hwq_map[WME_AC_BK];
                break;
        default:
                qnum = sc->tx.hwq_map[WME_AC_BE];
                break;
        }

        return qnum;
}

/Bj?rn

#4 lore raw
Quoted 12 lines · Bj?rn Smedman

2010/11/2 Felix Fietkau <[email protected]>:

Quoted 11 lines
drivers/net/wireless/ath/ath9k/xmit.c +2 -2
+       q = ath_get_mac80211_qnum(txq->axq_class, sc);
       r = ath_tx_setup_buffer(hw, bf, skb, txctl);
       if (unlikely(r)) {
               ath_print(common, ATH_DBG_FATAL, "TX mem alloc failure\n");
@@ -1756,8 +1757,8 @@ int ath_tx_start(struct ieee80211_hw *hw
                * we will at least have to run TX completionon one buffer
                * on the queue */
               spin_lock_bh(&txq->axq_lock);
-               if (!txq->stopped && txq->axq_depth > 1) {
-                       ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+               if (q >= 0 && !txq->stopped && txq->axq_depth > 1) {
Quoted 8 lines

drivers/net/wireless/ath/ath9k/xmit.c int ath_tx_start(struct ieee80211_hw *hw · line 1763

Quoted 3 lines
drivers/net/wireless/ath/ath9k/xmit.c +1 -0
+                       ath_mac80211_stop_queue(sc, q);
                       txq->stopped = 1;
               }

You cannot be sure that you are stopping the queue that the skb actually came in on here since mac80211 queues are mapped to hw queues by ath_get_hal_qnum() and that mapping is not reversible (due to the default statement):

How does the default statement matter here? The queue number always comes from an index of the ieee802_1d_to_ac[] array, which only contains numbers from 0 to 3. That should make the conversion reversible.

- Felix

#5 lore raw

2010/11/2 Felix Fietkau <[email protected]>:

Quoted 21 lines · Bj?rn Smedman
Quoted 12 lines

2010/11/2 Felix Fietkau <[email protected]>:

Quoted 11 lines

+ ? ? ? q = ath_get_mac80211_qnum(txq->axq_class, sc);
? ? ? ?r = ath_tx_setup_buffer(hw, bf, skb, txctl);
? ? ? ?if (unlikely(r)) {
? ? ? ? ? ? ? ?ath_print(common, ATH_DBG_FATAL, "TX mem alloc failure\n");

(quoted diff) +0 -0
@@ -1756,8 +1757,8 @@ int ath_tx_start(struct ieee80211_hw *hw

? ? ? ? ? ? ? ? * we will at least have to run TX completionon one buffer ? ? ? ? ? ? ? ? * on the queue */
? ? ? ? ? ? ? ?spin_lock_bh(&txq->axq_lock);
- ? ? ? ? ? ? ? if (!txq->stopped && txq->axq_depth > 1) {
- ? ? ? ? ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+ ? ? ? ? ? ? ? if (q >= 0 && !txq->stopped && txq->axq_depth > 1) {

Quoted 8 lines
Quoted 3 lines

+ ? ? ? ? ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, q); ? ? ? ? ? ? ? ? ? ? ? ?txq->stopped = 1;
? ? ? ? ? ? ? ?}

You cannot be sure that you are stopping the queue that the skb actually came in on here since mac80211 queues are mapped to hw queues by ath_get_hal_qnum() and that mapping is not reversible (due to the default statement):

Quoted 3 lines

How does the default statement matter here? The queue number always comes from an index of the ieee802_1d_to_ac[] array, which only contains numbers from 0 to 3. That should make the conversion reversible.

True, but then you have a functional dependency on that data/code (with catastrophic consequences if it ever changes). I understand the name of that array suggests that it will be fixed forever but I don't think we can be sure that a queue mapping will always be an AC. I think it may be very reasonable to expand it to be a TID (0-7) or even a separate queue per RA and TID. Are you prepared to put a BUG_ON() under that default? If so that's a start.

But it's not only the default statement that may make that mapping non-reversible. It could also be that e.g. sc->tx.hwq_map[WME_AC_VI] == sc->tx.hwq_map[WME_AC_VO]. You need some BUG_ONs there too and you better not try to support a chipset with less than 4 hw queues.

/Bj?rn

#6 lore raw

RFC 1/1 ath9k: fix tx queue selection

Quoted 34 lines · Bj?rn Smedman

2010/11/2 Felix Fietkau <[email protected]>:

Quoted 21 lines · Bj?rn Smedman
Quoted 12 lines

2010/11/2 Felix Fietkau <[email protected]>:

Quoted 11 lines
(quoted diff) +2 -2
+       q = ath_get_mac80211_qnum(txq->axq_class, sc);
       r = ath_tx_setup_buffer(hw, bf, skb, txctl);
       if (unlikely(r)) {
               ath_print(common, ATH_DBG_FATAL, "TX mem alloc failure\n");
@@ -1756,8 +1757,8 @@ int ath_tx_start(struct ieee80211_hw *hw
                * we will at least have to run TX completionon one buffer
                * on the queue */
               spin_lock_bh(&txq->axq_lock);
-               if (!txq->stopped && txq->axq_depth > 1) {
-                       ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+               if (q >= 0 && !txq->stopped && txq->axq_depth > 1) {
Quoted 8 lines

Review int ath_tx_start(struct ieee80211_hw *hw · line 1763

Quoted 3 lines
(quoted diff) +1 -0
+                       ath_mac80211_stop_queue(sc, q);
                       txq->stopped = 1;
               }

You cannot be sure that you are stopping the queue that the skb actually came in on here since mac80211 queues are mapped to hw queues by ath_get_hal_qnum() and that mapping is not reversible (due to the default statement):

Quoted 3 lines

How does the default statement matter here? The queue number always comes from an index of the ieee802_1d_to_ac[] array, which only contains numbers from 0 to 3. That should make the conversion reversible.

True, but then you have a functional dependency on that data/code (with catastrophic consequences if it ever changes). I understand the name of that array suggests that it will be fixed forever but I don't think we can be sure that a queue mapping will always be an AC. I think it may be very reasonable to expand it to be a TID (0-7) or even a separate queue per RA and TID. Are you prepared to put a BUG_ON() under that default? If so that's a start.

Quoted 4 lines

But it's not only the default statement that may make that mapping non-reversible. It could also be that e.g. sc->tx.hwq_map[WME_AC_VI] == sc->tx.hwq_map[WME_AC_VO]. You need some BUG_ONs there too and you better not try to support a chipset with less than 4 hw queues.

How about this then? I decoupled the WME_AC_* definitions from the ath9k_hw queue subtypes, so that I could redefine them to the numbers used by mac80211. That gets rid of another crappy abstraction. With this patch, pending frames will only be counted for the case where the txq is correct wrt. skb queue mapping.
I still don't think fetching the tid from the data buffer again is the right thing to do. I double checked ath9k's tid -> ac conversion and it looks correct to me.

drivers/net/wireless/ath/ath9k/ath9k.h +3 -6
@@ -195,7 +195,6 @@ enum ATH_AGGR_STATUS {
 
 #define ATH_TXFIFO_DEPTH 8
 struct ath_txq {
-	int axq_class;
 	u32 axq_qnum;
 	u32 *axq_link;
 	struct list_head axq_q;
@@ -208,11 +207,12 @@ struct ath_txq {
 	struct list_head txq_fifo_pending;
 	u8 txq_headidx;
 	u8 txq_tailidx;
+	int pending_frames;
 };
 
 struct ath_atx_ac {
+	struct ath_txq *txq;
 	int sched;
-	int qnum;
 	struct list_head list;
 	struct list_head tid_q;
 };
@@ -290,12 +290,11 @@ struct ath_tx_control {
 struct ath_tx {
 	u16 seq_no;
 	u32 txqsetup;
-	int hwq_map[WME_NUM_AC];
 	spinlock_t txbuflock;
 	struct list_head txbuf;
 	struct ath_txq txq[ATH9K_NUM_TX_QUEUES];
 	struct ath_descdma txdma;
-	int pending_frames[WME_NUM_AC];
+	struct ath_txq *txq_map[WME_NUM_AC];
 };
 
 struct ath_rx_edma {
@@ -325,7 +324,6 @@ void ath_rx_cleanup(struct ath_softc *sc
 int ath_rx_tasklet(struct ath_softc *sc, int flush, bool hp);
 struct ath_txq *ath_txq_setup(struct ath_softc *sc, int qtype, int subtype);
 void ath_tx_cleanupq(struct ath_softc *sc, struct ath_txq *txq);
-int ath_tx_setup(struct ath_softc *sc, int haltype);
 void ath_drain_all_txq(struct ath_softc *sc, bool retry_tx);
 void ath_draintxq(struct ath_softc *sc,
 		     struct ath_txq *txq, bool retry_tx);
@@ -665,7 +663,6 @@ struct ath_wiphy {
 
 void ath9k_tasklet(unsigned long data);
 int ath_reset(struct ath_softc *sc, bool retry_tx);
-int ath_get_mac80211_qnum(u32 queue, struct ath_softc *sc);
 int ath_cabq_update(struct ath_softc *);
 
 static inline void ath_read_cachesize(struct ath_common *common, int *csz)
drivers/net/wireless/ath/ath9k/beacon.c +3 -3
@@ -28,7 +28,7 @@ int ath_beaconq_config(struct ath_softc 
 	struct ath_hw *ah = sc->sc_ah;
 	struct ath_common *common = ath9k_hw_common(ah);
 	struct ath9k_tx_queue_info qi, qi_be;
-	int qnum;
+	struct ath_txq *txq;
 
 	ath9k_hw_get_txq_props(ah, sc->beacon.beaconq, &qi);
 	if (sc->sc_ah->opmode == NL80211_IFTYPE_AP) {
@@ -38,8 +38,8 @@ int ath_beaconq_config(struct ath_softc 
 		qi.tqi_cwmax = 0;
 	} else {
 		/* Adhoc mode; important thing is to use 2x cwmin. */
-		qnum = sc->tx.hwq_map[WME_AC_BE];
-		ath9k_hw_get_txq_props(ah, qnum, &qi_be);
+		txq = sc->tx.txq_map[WME_AC_BE];
+		ath9k_hw_get_txq_props(ah, txq->axq_qnum, &qi_be);
 		qi.tqi_aifs = qi_be.tqi_aifs;
 		qi.tqi_cwmin = 4*qi_be.tqi_cwmin;
 		qi.tqi_cwmax = qi_be.tqi_cwmax;
drivers/net/wireless/ath/ath9k/common.h +5 -4
@@ -31,10 +31,11 @@
 #define WME_MAX_BA              WME_BA_BMP_SIZE
 #define ATH_TID_MAX_BUFS        (2 * WME_MAX_BA)
 
-#define WME_AC_BE   0
-#define WME_AC_BK   1
-#define WME_AC_VI   2
-#define WME_AC_VO   3
+/* These must match mac80211 skb queue mapping numbers */
+#define WME_AC_VO   0
+#define WME_AC_VI   1
+#define WME_AC_BE   2
+#define WME_AC_BK   3
 #define WME_NUM_AC  4
 
 #define ATH_RSSI_DUMMY_MARKER   0x127
drivers/net/wireless/ath/ath9k/main.c +10 -61

128 lines not on this page · raw message

drivers/net/wireless/ath/ath9k/xmit.c +40 -53

225 lines not on this page · raw message

drivers/net/wireless/ath/ath9k/hw.h +7 -0
@@ -157,6 +157,13 @@
 #define PAPRD_GAIN_TABLE_ENTRIES    32
 #define PAPRD_TABLE_SZ              24
 
+enum ath_hw_txq_subtype {
+	ATH_TXQ_AC_BE = 0,
+	ATH_TXQ_AC_BK = 1,
+	ATH_TXQ_AC_VI = 2,
+	ATH_TXQ_AC_VO = 3,
+};
+
 enum ath_ini_subsys {
 	ATH_INI_PRE = 0,
 	ATH_INI_CORE,
drivers/net/wireless/ath/ath9k/htc_drv_txrx.c +8 -1
@@ -20,8 +20,15 @@
 /* TX */
 /******/
 
+static const int subtype_txq_to_hwq[] = {
+	[WME_AC_BE] = ATH_TXQ_AC_BE,
+	[WME_AC_BK] = ATH_TXQ_AC_BK,
+	[WME_AC_VI] = ATH_TXQ_AC_VI,
+	[WME_AC_VO] = ATH_TXQ_AC_VO,
+};
+
 #define ATH9K_HTC_INIT_TXQ(subtype) do {			\
-		qi.tqi_subtype = subtype;			\
+		qi.tqi_subtype = subtype_txq_to_hwq[subtype];	\
 		qi.tqi_aifs = ATH9K_TXQ_USEDEFAULT;		\
 		qi.tqi_cwmin = ATH9K_TXQ_USEDEFAULT;		\
 		qi.tqi_cwmax = ATH9K_TXQ_USEDEFAULT;		\
drivers/net/wireless/ath/ath9k/init.c +6 -46

80 lines not on this page · raw message

drivers/net/wireless/ath/ath9k/virtual.c +1 -1
@@ -187,7 +187,7 @@ static int ath9k_send_nullfunc(struct at
 	info->control.rates[1].idx = -1;
 
 	memset(&txctl, 0, sizeof(struct ath_tx_control));
-	txctl.txq = &sc->tx.txq[sc->tx.hwq_map[WME_AC_VO]];
+	txctl.txq = sc->tx.txq_map[WME_AC_VO];
 	txctl.frame_type = ps ? ATH9K_IFT_PAUSE : ATH9K_IFT_UNPAUSE;
 
 	if (ath_tx_start(aphy->hw, skb, &txctl) != 0)
drivers/net/wireless/ath/ath9k/debug.c +19 -17
@@ -579,10 +579,10 @@ static const struct file_operations fops
 	do {								\
 		len += snprintf(buf + len, size - len,			\
 				"%s%13u%11u%10u%10u\n", str,		\
-		sc->debug.stats.txstats[sc->tx.hwq_map[WME_AC_BE]].elem, \
-		sc->debug.stats.txstats[sc->tx.hwq_map[WME_AC_BK]].elem, \
-		sc->debug.stats.txstats[sc->tx.hwq_map[WME_AC_VI]].elem, \
-		sc->debug.stats.txstats[sc->tx.hwq_map[WME_AC_VO]].elem); \
+		sc->debug.stats.txstats[WME_AC_BE].elem, \
+		sc->debug.stats.txstats[WME_AC_BK].elem, \
+		sc->debug.stats.txstats[WME_AC_VI].elem, \
+		sc->debug.stats.txstats[WME_AC_VO].elem); \
 } while(0)
 
 static ssize_t read_file_xmit(struct file *file, char __user *user_buf,
@@ -624,33 +624,35 @@ static ssize_t read_file_xmit(struct fil
 	return retval;
 }
 
-void ath_debug_stat_tx(struct ath_softc *sc, struct ath_txq *txq,
-		       struct ath_buf *bf, struct ath_tx_status *ts)
+void ath_debug_stat_tx(struct ath_softc *sc, struct ath_buf *bf,
+		       struct ath_tx_status *ts)
 {
-	TX_STAT_INC(txq->axq_qnum, tx_pkts_all);
-	sc->debug.stats.txstats[txq->axq_qnum].tx_bytes_all += bf->bf_mpdu->len;
+	int qnum = skb_get_queue_mapping(bf->bf_mpdu);
+
+	TX_STAT_INC(qnum, tx_pkts_all);
+	sc->debug.stats.txstats[qnum].tx_bytes_all += bf->bf_mpdu->len;
 
 	if (bf_isampdu(bf)) {
 		if (bf_isxretried(bf))
-			TX_STAT_INC(txq->axq_qnum, a_xretries);
+			TX_STAT_INC(qnum, a_xretries);
 		else
-			TX_STAT_INC(txq->axq_qnum, a_completed);
+			TX_STAT_INC(qnum, a_completed);
 	} else {
-		TX_STAT_INC(txq->axq_qnum, completed);
+		TX_STAT_INC(qnum, completed);
 	}
 
 	if (ts->ts_status & ATH9K_TXERR_FIFO)
-		TX_STAT_INC(txq->axq_qnum, fifo_underrun);
+		TX_STAT_INC(qnum, fifo_underrun);
 	if (ts->ts_status & ATH9K_TXERR_XTXOP)
-		TX_STAT_INC(txq->axq_qnum, xtxop);
+		TX_STAT_INC(qnum, xtxop);
 	if (ts->ts_status & ATH9K_TXERR_TIMER_EXPIRED)
-		TX_STAT_INC(txq->axq_qnum, timer_exp);
+		TX_STAT_INC(qnum, timer_exp);
 	if (ts->ts_flags & ATH9K_TX_DESC_CFG_ERR)
-		TX_STAT_INC(txq->axq_qnum, desc_cfg_err);
+		TX_STAT_INC(qnum, desc_cfg_err);
 	if (ts->ts_flags & ATH9K_TX_DATA_UNDERRUN)
-		TX_STAT_INC(txq->axq_qnum, data_underrun);
+		TX_STAT_INC(qnum, data_underrun);
 	if (ts->ts_flags & ATH9K_TX_DELIM_UNDERRUN)
-		TX_STAT_INC(txq->axq_qnum, delim_underrun);
+		TX_STAT_INC(qnum, delim_underrun);
 }
 
 static const struct file_operations fops_xmit = {
#7 lore raw

2010/11/2 Felix Fietkau <[email protected]>:

Quoted 39 lines · Bj?rn Smedman
Quoted 34 lines

2010/11/2 Felix Fietkau <[email protected]>:

Quoted 21 lines · Bj?rn Smedman
Quoted 12 lines

2010/11/2 Felix Fietkau <[email protected]>:

Quoted 11 lines

+ ? ? ? q = ath_get_mac80211_qnum(txq->axq_class, sc);
? ? ? ?r = ath_tx_setup_buffer(hw, bf, skb, txctl);
? ? ? ?if (unlikely(r)) {
? ? ? ? ? ? ? ?ath_print(common, ATH_DBG_FATAL, "TX mem alloc failure\n");

(quoted diff) +0 -0
@@ -1756,8 +1757,8 @@ int ath_tx_start(struct ieee80211_hw *hw

? ? ? ? ? ? ? ? * we will at least have to run TX completionon one buffer ? ? ? ? ? ? ? ? * on the queue */
? ? ? ? ? ? ? ?spin_lock_bh(&txq->axq_lock);
- ? ? ? ? ? ? ? if (!txq->stopped && txq->axq_depth > 1) {
- ? ? ? ? ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+ ? ? ? ? ? ? ? if (q >= 0 && !txq->stopped && txq->axq_depth > 1) {

Quoted 8 lines
Quoted 3 lines

+ ? ? ? ? ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, q); ? ? ? ? ? ? ? ? ? ? ? ?txq->stopped = 1;
? ? ? ? ? ? ? ?}

You cannot be sure that you are stopping the queue that the skb actually came in on here since mac80211 queues are mapped to hw queues by ath_get_hal_qnum() and that mapping is not reversible (due to the default statement):

Quoted 3 lines

How does the default statement matter here? The queue number always comes from an index of the ieee802_1d_to_ac[] array, which only contains numbers from 0 to 3. That should make the conversion reversible.

True, but then you have a functional dependency on that data/code (with catastrophic consequences if it ever changes). I understand the name of that array suggests that it will be fixed forever but I don't think we can be sure that a queue mapping will always be an AC. I think it may be very reasonable to expand it to be a TID (0-7) or even a separate queue per RA and TID. Are you prepared to put a BUG_ON() under that default? If so that's a start.

Quoted 4 lines

But it's not only the default statement that may make that mapping non-reversible. It could also be that e.g. sc->tx.hwq_map[WME_AC_VI] == sc->tx.hwq_map[WME_AC_VO]. You need some BUG_ONs there too and you better not try to support a chipset with less than 4 hw queues.

Quoted 8 lines

How about this then? I decoupled the WME_AC_* definitions from the ath9k_hw queue subtypes, so that I could redefine them to the numbers used by mac80211. That gets rid of another crappy abstraction. With this patch, pending frames will only be counted for the case where the txq is correct wrt. skb queue mapping.
I still don't think fetching the tid from the data buffer again is the right thing to do. I double checked ath9k's tid -> ac conversion and it looks correct to me.

This is one good looking patch. :) And I agree, looking at the header qos is good to avoid.

But there is still the risk of queue selection mismatch as I see it... See comments below.

/Bj?rn

Quoted 158 lines
drivers/net/wireless/ath/ath9k/ath9k.h +0 -0
@@ -195,7 +195,6 @@ enum ATH_AGGR_STATUS {
 

?#define ATH_TXFIFO_DEPTH 8
?struct ath_txq {
- ? ? ? int axq_class;
? ? ? ?u32 axq_qnum;
? ? ? ?u32 *axq_link;
? ? ? ?struct list_head axq_q;

drivers/net/wireless/ath/ath9k/ath9k.h +3 -5
@@ -208,11 +207,12 @@ struct ath_txq {
 ? ? ? ?struct list_head txq_fifo_pending;
 ? ? ? ?u8 txq_headidx;
 ? ? ? ?u8 txq_tailidx;
+ ? ? ? int pending_frames;
 ?};
 
 ?struct ath_atx_ac {
+ ? ? ? struct ath_txq *txq;
 ? ? ? ?int sched;
- ? ? ? int qnum;
 ? ? ? ?struct list_head list;
 ? ? ? ?struct list_head tid_q;
 ?};
@@ -290,12 +290,11 @@ struct ath_tx_control {
 ?struct ath_tx {
 ? ? ? ?u16 seq_no;
 ? ? ? ?u32 txqsetup;
- ? ? ? int hwq_map[WME_NUM_AC];
 ? ? ? ?spinlock_t txbuflock;
 ? ? ? ?struct list_head txbuf;
 ? ? ? ?struct ath_txq txq[ATH9K_NUM_TX_QUEUES];
 ? ? ? ?struct ath_descdma txdma;
- ? ? ? int pending_frames[WME_NUM_AC];
+ ? ? ? struct ath_txq *txq_map[WME_NUM_AC];
 ?};
 
 ?struct ath_rx_edma {
@@ -325,7 +324,6 @@ void ath_rx_cleanup(struct ath_softc *sc
 ?int ath_rx_tasklet(struct ath_softc *sc, int flush, bool hp);
 ?struct ath_txq *ath_txq_setup(struct ath_softc *sc, int qtype, int subtype);
 ?void ath_tx_cleanupq(struct ath_softc *sc, struct ath_txq *txq);
-int ath_tx_setup(struct ath_softc *sc, int haltype);
 ?void ath_drain_all_txq(struct ath_softc *sc, bool retry_tx);
 ?void ath_draintxq(struct ath_softc *sc,
 ? ? ? ? ? ? ? ? ? ? struct ath_txq *txq, bool retry_tx);
@@ -665,7 +663,6 @@ struct ath_wiphy {
 
 ?void ath9k_tasklet(unsigned long data);
 ?int ath_reset(struct ath_softc *sc, bool retry_tx);
-int ath_get_mac80211_qnum(u32 queue, struct ath_softc *sc);
 ?int ath_cabq_update(struct ath_softc *);
 
 ?static inline void ath_read_cachesize(struct ath_common *common, int *csz)
drivers/net/wireless/ath/ath9k/beacon.c +1 -1
@@ -28,7 +28,7 @@ int ath_beaconq_config(struct ath_softc
 ? ? ? ?struct ath_hw *ah = sc->sc_ah;
 ? ? ? ?struct ath_common *common = ath9k_hw_common(ah);
 ? ? ? ?struct ath9k_tx_queue_info qi, qi_be;
- ? ? ? int qnum;
+ ? ? ? struct ath_txq *txq;
 
 ? ? ? ?ath9k_hw_get_txq_props(ah, sc->beacon.beaconq, &qi);
 ? ? ? ?if (sc->sc_ah->opmode == NL80211_IFTYPE_AP) {
@@ -38,8 +38,8 @@ int ath_beaconq_config(struct ath_softc
 ? ? ? ? ? ? ? ?qi.tqi_cwmax = 0;
 ? ? ? ?} else {

? ? ? ? ? ? ? ?/* Adhoc mode; important thing is to use 2x cwmin. */
- ? ? ? ? ? ? ? qnum = sc->tx.hwq_map[WME_AC_BE];
- ? ? ? ? ? ? ? ath9k_hw_get_txq_props(ah, qnum, &qi_be);
+ ? ? ? ? ? ? ? txq = sc->tx.txq_map[WME_AC_BE];
+ ? ? ? ? ? ? ? ath9k_hw_get_txq_props(ah, txq->axq_qnum, &qi_be); ? ? ? ? ? ? ? ?qi.tqi_aifs = qi_be.tqi_aifs;
? ? ? ? ? ? ? ?qi.tqi_cwmin = 4*qi_be.tqi_cwmin;
? ? ? ? ? ? ? ?qi.tqi_cwmax = qi_be.tqi_cwmax;

drivers/net/wireless/ath/ath9k/common.h +0 -0
@@ -31,10 +31,11 @@

?#define WME_MAX_BA ? ? ? ? ? ? ?WME_BA_BMP_SIZE
?#define ATH_TID_MAX_BUFS ? ? ? ?(2 * WME_MAX_BA)

drivers/net/wireless/ath/ath9k/common.h +5 -4
-#define WME_AC_BE ? 0
-#define WME_AC_BK ? 1
-#define WME_AC_VI ? 2
-#define WME_AC_VO ? 3
+/* These must match mac80211 skb queue mapping numbers */
+#define WME_AC_VO ? 0
+#define WME_AC_VI ? 1
+#define WME_AC_BE ? 2
+#define WME_AC_BK ? 3

?#define WME_NUM_AC ?4

?#define ATH_RSSI_DUMMY_MARKER ? 0x127

drivers/net/wireless/ath/ath9k/main.c +2 -42
@@ -331,7 +331,7 @@ void ath_paprd_calibrate(struct work_str
 ? ? ? ?struct ath_tx_control txctl;
 ? ? ? ?struct ath9k_hw_cal_data *caldata = ah->caldata;
 ? ? ? ?struct ath_common *common = ath9k_hw_common(ah);
- ? ? ? int qnum, ftype;
+ ? ? ? int ftype;
 ? ? ? ?int chain_ok = 0;
 ? ? ? ?int chain;
 ? ? ? ?int len = 1800;
@@ -358,8 +358,7 @@ void ath_paprd_calibrate(struct work_str
 ? ? ? ?memcpy(hdr->addr3, hw->wiphy->perm_addr, ETH_ALEN);
 
 ? ? ? ?memset(&txctl, 0, sizeof(txctl));
- ? ? ? qnum = sc->tx.hwq_map[WME_AC_BE];
- ? ? ? txctl.txq = &sc->tx.txq[qnum];
+ ? ? ? txctl.txq = sc->tx.txq_map[WME_AC_BE];
 
 ? ? ? ?ath9k_ps_wakeup(sc);
 ? ? ? ?ar9003_paprd_init_table(ah);
@@ -1025,56 +1024,6 @@ int ath_reset(struct ath_softc *sc, bool
 ? ? ? ?return r;
 ?}
 
-static int ath_get_hal_qnum(u16 queue, struct ath_softc *sc)
-{
- ? ? ? int qnum;
-
- ? ? ? switch (queue) {
- ? ? ? case 0:
- ? ? ? ? ? ? ? qnum = sc->tx.hwq_map[WME_AC_VO];
- ? ? ? ? ? ? ? break;
- ? ? ? case 1:
- ? ? ? ? ? ? ? qnum = sc->tx.hwq_map[WME_AC_VI];
- ? ? ? ? ? ? ? break;
- ? ? ? case 2:
- ? ? ? ? ? ? ? qnum = sc->tx.hwq_map[WME_AC_BE];
- ? ? ? ? ? ? ? break;
- ? ? ? case 3:
- ? ? ? ? ? ? ? qnum = sc->tx.hwq_map[WME_AC_BK];
- ? ? ? ? ? ? ? break;
- ? ? ? default:
- ? ? ? ? ? ? ? qnum = sc->tx.hwq_map[WME_AC_BE];
- ? ? ? ? ? ? ? break;
- ? ? ? }
-
- ? ? ? return qnum;
-}
-
-int ath_get_mac80211_qnum(u32 queue, struct ath_softc *sc)
-{
- ? ? ? int qnum;
-
- ? ? ? switch (queue) {
- ? ? ? case WME_AC_VO:
- ? ? ? ? ? ? ? qnum = 0;
- ? ? ? ? ? ? ? break;
- ? ? ? case WME_AC_VI:
- ? ? ? ? ? ? ? qnum = 1;
- ? ? ? ? ? ? ? break;
- ? ? ? case WME_AC_BE:
- ? ? ? ? ? ? ? qnum = 2;
- ? ? ? ? ? ? ? break;

drivers/net/wireless/ath/ath9k/main.c int ath_reset(struct ath_softc *sc, bool · line 1076

Quoted 10 lines
drivers/net/wireless/ath/ath9k/main.c +0 -10
- ? ? ? case WME_AC_BK:
- ? ? ? ? ? ? ? qnum = 3;
- ? ? ? ? ? ? ? break;
- ? ? ? default:
- ? ? ? ? ? ? ? qnum = -1;
- ? ? ? ? ? ? ? break;
- ? ? ? }
-
- ? ? ? return qnum;
-}

Nice to see this go. This I like. :)

Quoted 13 lines
drivers/net/wireless/ath/ath9k/main.c +0 -1
-

?/* XXX: Remove me once we don't depend on ath9k_channel for all ?* this redundant data */
?void ath9k_update_ichannel(struct ath_softc *sc, struct ieee80211_hw *hw,

drivers/net/wireless/ath/ath9k/main.c +0 -1
@@ -1244,7 +1193,6 @@ static int ath9k_tx(struct ieee80211_hw
 ? ? ? ?struct ath_tx_control txctl;
 ? ? ? ?int padpos, padsize;
 ? ? ? ?struct ieee80211_hdr *hdr = (struct ieee80211_hdr *) skb->data;
- ? ? ? int qnum;
 
 ? ? ? ?if (aphy->state != ATH_WIPHY_ACTIVE && aphy->state != ATH_WIPHY_SCAN) {
 ? ? ? ? ? ? ? ?ath_print(common, ATH_DBG_XMIT,

drivers/net/wireless/ath/ath9k/main.c static int ath9k_tx(struct ieee80211_hw · line 1268

Quoted 6 lines
drivers/net/wireless/ath/ath9k/main.c +1 -2
@@ -1317,8 +1265,7 @@ static int ath9k_tx(struct ieee80211_hw
 ? ? ? ? ? ? ? ?memmove(skb->data, skb->data + padsize, padpos);
 ? ? ? ?}
 
- ? ? ? qnum = ath_get_hal_qnum(skb_get_queue_mapping(skb), sc);
- ? ? ? txctl.txq = &sc->tx.txq[qnum];
+ ? ? ? txctl.txq = sc->tx.txq_map[skb_get_queue_mapping(skb)];

Could we be indexing txq_map[] out of bounds here? I guess this question is the fundamental one: can we be sure that skb_get_queue_mapping(skb) will return an AC i.e. range 0-3? Not only now but forever? Or do we need a comment in mac80211 saying driver will crash if anything else is returned?

Quoted 133 lines
drivers/net/wireless/ath/ath9k/main.c +4 -2
 ? ? ? ?ath_print(common, ATH_DBG_XMIT, "transmitting packet, skb: %p\n", skb);
 
@@ -1802,12 +1749,15 @@ static int ath9k_conf_tx(struct ieee8021
 ? ? ? ?struct ath_wiphy *aphy = hw->priv;
 ? ? ? ?struct ath_softc *sc = aphy->sc;
 ? ? ? ?struct ath_common *common = ath9k_hw_common(sc->sc_ah);
+ ? ? ? struct ath_txq *txq;
 ? ? ? ?struct ath9k_tx_queue_info qi;
- ? ? ? int ret = 0, qnum;
+ ? ? ? int ret = 0;
 
 ? ? ? ?if (queue >= WME_NUM_AC)
 ? ? ? ? ? ? ? ?return 0;
 
+ ? ? ? txq = sc->tx.txq_map[queue];
+
 ? ? ? ?mutex_lock(&sc->mutex);
 
 ? ? ? ?memset(&qi, 0, sizeof(struct ath9k_tx_queue_info));
@@ -1816,20 +1766,19 @@ static int ath9k_conf_tx(struct ieee8021
 ? ? ? ?qi.tqi_cwmin = params->cw_min;
 ? ? ? ?qi.tqi_cwmax = params->cw_max;
 ? ? ? ?qi.tqi_burstTime = params->txop;
- ? ? ? qnum = ath_get_hal_qnum(queue, sc);
 
 ? ? ? ?ath_print(common, ATH_DBG_CONFIG,

? ? ? ? ? ? ? ? ?"Configure tx [queue/halq] [%d/%d], ?"
? ? ? ? ? ? ? ? ?"aifs: %d, cw_min: %d, cw_max: %d, txop: %d\n",
- ? ? ? ? ? ? ? ? queue, qnum, params->aifs, params->cw_min,
+ ? ? ? ? ? ? ? ? queue, txq->axq_qnum, params->aifs, params->cw_min, ? ? ? ? ? ? ? ? ?params->cw_max, params->txop);

- ? ? ? ret = ath_txq_update(sc, qnum, &qi);
+ ? ? ? ret = ath_txq_update(sc, txq->axq_qnum, &qi);
? ? ? ?if (ret)
? ? ? ? ? ? ? ?ath_print(common, ATH_DBG_FATAL, "TXQ Update failed\n");

? ? ? ?if (sc->sc_ah->opmode == NL80211_IFTYPE_ADHOC)
- ? ? ? ? ? ? ? if ((qnum == sc->tx.hwq_map[WME_AC_BE]) && !ret)
+ ? ? ? ? ? ? ? if (queue == WME_AC_BE && !ret)
? ? ? ? ? ? ? ? ? ? ? ?ath_beaconq_config(sc);

? ? ? ?mutex_unlock(&sc->mutex);

drivers/net/wireless/ath/ath9k/xmit.c +10 -23
@@ -124,7 +124,7 @@ static void ath_tx_queue_tid(struct ath_
 
 ?static void ath_tx_resume_tid(struct ath_softc *sc, struct ath_atx_tid *tid)
 ?{
- ? ? ? struct ath_txq *txq = &sc->tx.txq[tid->ac->qnum];
+ ? ? ? struct ath_txq *txq = tid->ac->txq;
 
 ? ? ? ?WARN_ON(!tid->paused);
 
@@ -142,7 +142,7 @@ unlock:
 
 ?static void ath_tx_flush_tid(struct ath_softc *sc, struct ath_atx_tid *tid)
 ?{
- ? ? ? struct ath_txq *txq = &sc->tx.txq[tid->ac->qnum];
+ ? ? ? struct ath_txq *txq = tid->ac->txq;
 ? ? ? ?struct ath_buf *bf;
 ? ? ? ?struct list_head bf_head;
 ? ? ? ?struct ath_tx_status ts;
@@ -817,7 +817,7 @@ void ath_tx_aggr_stop(struct ath_softc *
 ?{
 ? ? ? ?struct ath_node *an = (struct ath_node *)sta->drv_priv;
 ? ? ? ?struct ath_atx_tid *txtid = ATH_AN_2_TID(an, tid);
- ? ? ? struct ath_txq *txq = &sc->tx.txq[txtid->ac->qnum];
+ ? ? ? struct ath_txq *txq = txtid->ac->txq;
 
 ? ? ? ?if (txtid->state & AGGR_CLEANUP)
 ? ? ? ? ? ? ? ?return;
@@ -888,10 +888,16 @@ struct ath_txq *ath_txq_setup(struct ath
 ? ? ? ?struct ath_hw *ah = sc->sc_ah;
 ? ? ? ?struct ath_common *common = ath9k_hw_common(ah);
 ? ? ? ?struct ath9k_tx_queue_info qi;
+ ? ? ? static const int subtype_txq_to_hwq[] = {
+ ? ? ? ? ? ? ? [WME_AC_BE] = ATH_TXQ_AC_BE,
+ ? ? ? ? ? ? ? [WME_AC_BK] = ATH_TXQ_AC_BK,
+ ? ? ? ? ? ? ? [WME_AC_VI] = ATH_TXQ_AC_VI,
+ ? ? ? ? ? ? ? [WME_AC_VO] = ATH_TXQ_AC_VO,
+ ? ? ? };
 ? ? ? ?int qnum, i;
 
 ? ? ? ?memset(&qi, 0, sizeof(qi));
- ? ? ? qi.tqi_subtype = subtype;
+ ? ? ? qi.tqi_subtype = subtype_txq_to_hwq[subtype];
 ? ? ? ?qi.tqi_aifs = ATH9K_TXQ_USEDEFAULT;
 ? ? ? ?qi.tqi_cwmin = ATH9K_TXQ_USEDEFAULT;
 ? ? ? ?qi.tqi_cwmax = ATH9K_TXQ_USEDEFAULT;
@@ -940,7 +946,6 @@ struct ath_txq *ath_txq_setup(struct ath
 ? ? ? ?if (!ATH_TXQ_SETUP(sc, qnum)) {
 ? ? ? ? ? ? ? ?struct ath_txq *txq = &sc->tx.txq[qnum];
 
- ? ? ? ? ? ? ? txq->axq_class = subtype;
 ? ? ? ? ? ? ? ?txq->axq_qnum = qnum;
 ? ? ? ? ? ? ? ?txq->axq_link = NULL;
 ? ? ? ? ? ? ? ?INIT_LIST_HEAD(&txq->axq_q);
@@ -1210,24 +1215,6 @@ void ath_txq_schedule(struct ath_softc *
 ? ? ? ?}
 ?}
 
-int ath_tx_setup(struct ath_softc *sc, int haltype)
-{
- ? ? ? struct ath_txq *txq;
-
- ? ? ? if (haltype >= ARRAY_SIZE(sc->tx.hwq_map)) {
- ? ? ? ? ? ? ? ath_print(ath9k_hw_common(sc->sc_ah), ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "HAL AC %u out of range, max %zu!\n",
- ? ? ? ? ? ? ? ? ? ? ? ?haltype, ARRAY_SIZE(sc->tx.hwq_map));
- ? ? ? ? ? ? ? return 0;
- ? ? ? }
- ? ? ? txq = ath_txq_setup(sc, ATH9K_TX_QUEUE_DATA, haltype);
- ? ? ? if (txq != NULL) {
- ? ? ? ? ? ? ? sc->tx.hwq_map[haltype] = txq->axq_qnum;
- ? ? ? ? ? ? ? return 1;
- ? ? ? } else
- ? ? ? ? ? ? ? return 0;
-}
-

?/***********/
?/* TX, DMA */
?/***********/

drivers/net/wireless/ath/ath9k/xmit.c +1 -0
@@ -1747,6 +1734,7 @@ int ath_tx_start(struct ieee80211_hw *hw
 ? ? ? ? ? ? ? ?return -1;
 ? ? ? ?}
 
+ ? ? ? q = skb_get_queue_mapping(skb);
 ? ? ? ?r = ath_tx_setup_buffer(hw, bf, skb, txctl);
 ? ? ? ?if (unlikely(r)) {
 ? ? ? ? ? ? ? ?ath_print(common, ATH_DBG_FATAL, "TX mem alloc failure\n");
@@ -1756,8 +1744,9 @@ int ath_tx_start(struct ieee80211_hw *hw
Quoted 8 lines

? ? ? ? ? ? ? ? * we will at least have to run TX completionon one buffer ? ? ? ? ? ? ? ? * on the queue */
? ? ? ? ? ? ? ?spin_lock_bh(&txq->axq_lock);
- ? ? ? ? ? ? ? if (!txq->stopped && txq->axq_depth > 1) {
- ? ? ? ? ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+ ? ? ? ? ? ? ? if (txq == sc->tx.txq_map[q] && !txq->stopped &&
+ ? ? ? ? ? ? ? ? ? txq->axq_depth > 1) {
+ ? ? ? ? ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, q);

Again, possible index out of bounds, no? Also, what happens if txq != sc->tx.txq_map[q]? I guess that's less catastrophic but still; meaningful code will not execute.

Quoted 7 lines

? ? ? ? ? ? ? ? ? ? ? ?txq->stopped = 1;
? ? ? ? ? ? ? ?}
? ? ? ? ? ? ? ?spin_unlock_bh(&txq->axq_lock);

drivers/net/wireless/ath/ath9k/xmit.c +0 -0
@@ -1767,13 +1756,10 @@ int ath_tx_start(struct ieee80211_hw *hw
 ? ? ? ? ? ? ? ?return r;
 ? ? ? ?}
 

drivers/net/wireless/ath/ath9k/xmit.c int ath_tx_start(struct ieee80211_hw *hw · line 1762

Quoted 10 lines
drivers/net/wireless/ath/ath9k/xmit.c +3 -6
- ? ? ? q = skb_get_queue_mapping(skb);
- ? ? ? if (q >= 4)
- ? ? ? ? ? ? ? q = 0;
-
 ? ? ? ?spin_lock_bh(&txq->axq_lock);
- ? ? ? if (++sc->tx.pending_frames[q] > ATH_MAX_QDEPTH && !txq->stopped) {
- ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+ ? ? ? if (txq == sc->tx.txq_map[q] &&
+ ? ? ? ? ? ++txq->pending_frames > ATH_MAX_QDEPTH && !txq->stopped) {
+ ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, q);

Same as above.

Quoted 8 lines
drivers/net/wireless/ath/ath9k/xmit.c +0 -1
 ? ? ? ? ? ? ? ?txq->stopped = 1;
 ? ? ? ?}
 ? ? ? ?spin_unlock_bh(&txq->axq_lock);
@@ -1887,12 +1873,12 @@ static void ath_tx_complete(struct ath_s
 ? ? ? ?if (unlikely(tx_info->pad[0] & ATH_TX_INFO_FRAME_TYPE_INTERNAL))
 ? ? ? ? ? ? ? ?ath9k_tx_status(hw, skb);
 ? ? ? ?else {
- ? ? ? ? ? ? ? q = skb_get_queue_mapping(skb);

drivers/net/wireless/ath/ath9k/xmit.c static void ath_tx_complete(struct ath_s · line 1881

Quoted 10 lines
drivers/net/wireless/ath/ath9k/xmit.c +5 -4
- ? ? ? ? ? ? ? if (q >= 4)
- ? ? ? ? ? ? ? ? ? ? ? q = 0;
+ ? ? ? ? ? ? ? struct ath_txq *txq;
 
- ? ? ? ? ? ? ? if (--sc->tx.pending_frames[q] < 0)
- ? ? ? ? ? ? ? ? ? ? ? sc->tx.pending_frames[q] = 0;
+ ? ? ? ? ? ? ? q = skb_get_queue_mapping(skb);
+ ? ? ? ? ? ? ? txq = sc->tx.txq_map[q];
+ ? ? ? ? ? ? ? if (--txq->pending_frames < 0)
+ ? ? ? ? ? ? ? ? ? ? ? txq->pending_frames = 0;

This is off topic, cut do we really need this? Where do those missing frames go? :) I would much prefer a BUG_ON(txq->pending_frames < 0).

Quoted 52 lines
drivers/net/wireless/ath/ath9k/xmit.c +0 -0
 ? ? ? ? ? ? ? ?ieee80211_tx_status(hw, skb);
 ? ? ? ?}
@@ -1927,7 +1913,7 @@ static void ath_tx_complete_buf(struct a

? ? ? ? ? ? ? ?else
? ? ? ? ? ? ? ? ? ? ? ?complete(&sc->paprd_complete);
? ? ? ?} else {
- ? ? ? ? ? ? ? ath_debug_stat_tx(sc, txq, bf, ts);
+ ? ? ? ? ? ? ? ath_debug_stat_tx(sc, bf, ts);
? ? ? ? ? ? ? ?ath_tx_complete(sc, skb, bf->aphy, tx_flags);
? ? ? ?}
? ? ? ?/* At this point, skb (bf->bf_mpdu) is consumed...make sure we don't

drivers/net/wireless/ath/ath9k/xmit.c +7 -7
@@ -2018,16 +2004,13 @@ static void ath_tx_rc_status(struct ath_
 ? ? ? ?tx_info->status.rates[tx_rateindex].count = ts->ts_longretry + 1;
 ?}
 
-static void ath_wake_mac80211_queue(struct ath_softc *sc, struct ath_txq *txq)
+static void ath_wake_mac80211_queue(struct ath_softc *sc, int qnum)
 ?{
- ? ? ? int qnum;
-
- ? ? ? qnum = ath_get_mac80211_qnum(txq->axq_class, sc);
- ? ? ? if (qnum == -1)
- ? ? ? ? ? ? ? return;
+ ? ? ? struct ath_txq *txq;
 
+ ? ? ? txq = sc->tx.txq_map[qnum];
 ? ? ? ?spin_lock_bh(&txq->axq_lock);
- ? ? ? if (txq->stopped && sc->tx.pending_frames[qnum] < ATH_MAX_QDEPTH) {
+ ? ? ? if (txq->stopped && txq->pending_frames < ATH_MAX_QDEPTH) {
 ? ? ? ? ? ? ? ?if (ath_mac80211_start_queue(sc, qnum))
 ? ? ? ? ? ? ? ? ? ? ? ?txq->stopped = 0;
 ? ? ? ?}
@@ -2044,6 +2027,7 @@ static void ath_tx_processq(struct ath_s
 ? ? ? ?struct ath_tx_status ts;
 ? ? ? ?int txok;
 ? ? ? ?int status;
+ ? ? ? int qnum;
 
 ? ? ? ?ath_print(common, ATH_DBG_QUEUE, "tx queue %d (%x), link %p\n",
 ? ? ? ? ? ? ? ? ?txq->axq_qnum, ath9k_hw_gettxbuf(sc->sc_ah, txq->axq_qnum),
@@ -2119,12 +2103,15 @@ static void ath_tx_processq(struct ath_s
 ? ? ? ? ? ? ? ? ? ? ? ?ath_tx_rc_status(bf, &ts, txok ? 0 : 1, txok, true);
 ? ? ? ? ? ? ? ?}
 
+ ? ? ? ? ? ? ? qnum = skb_get_queue_mapping(bf->bf_mpdu);
+
 ? ? ? ? ? ? ? ?if (bf_isampdu(bf))
 ? ? ? ? ? ? ? ? ? ? ? ?ath_tx_complete_aggr(sc, txq, bf, &bf_head, &ts, txok);

? ? ? ? ? ? ? ?else
? ? ? ? ? ? ? ? ? ? ? ?ath_tx_complete_buf(sc, bf, txq, &bf_head, &ts, txok, 0);

Quoted 3 lines

- ? ? ? ? ? ? ? ath_wake_mac80211_queue(sc, txq);
+ ? ? ? ? ? ? ? if (txq == sc->tx.txq_map[qnum])
+ ? ? ? ? ? ? ? ? ? ? ? ath_wake_mac80211_queue(sc, qnum);

Out of bounds? But I like the fact that we are selecting the queue to start based on skb_get_queue_mapping(bf->bf_mpdu). :)

Quoted 23 lines

? ? ? ? ? ? ? ?spin_lock_bh(&txq->axq_lock);
? ? ? ? ? ? ? ?if (sc->sc_flags & SC_OP_TXAGGR)

drivers/net/wireless/ath/ath9k/xmit.c +3 -0
@@ -2194,6 +2181,7 @@ void ath_tx_edma_tasklet(struct ath_soft
 ? ? ? ?struct list_head bf_head;
 ? ? ? ?int status;
 ? ? ? ?int txok;
+ ? ? ? int qnum;
 
 ? ? ? ?for (;;) {
 ? ? ? ? ? ? ? ?status = ath9k_hw_txprocdesc(ah, NULL, (void *)&txs);
@@ -2237,13 +2225,16 @@ void ath_tx_edma_tasklet(struct ath_soft
 ? ? ? ? ? ? ? ? ? ? ? ?ath_tx_rc_status(bf, &txs, txok ? 0 : 1, txok, true);
 ? ? ? ? ? ? ? ?}
 
+ ? ? ? ? ? ? ? qnum = skb_get_queue_mapping(bf->bf_mpdu);
+
 ? ? ? ? ? ? ? ?if (bf_isampdu(bf))
 ? ? ? ? ? ? ? ? ? ? ? ?ath_tx_complete_aggr(sc, txq, bf, &bf_head, &txs, txok);

? ? ? ? ? ? ? ?else
? ? ? ? ? ? ? ? ? ? ? ?ath_tx_complete_buf(sc, bf, txq, &bf_head, ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?&txs, txok, 0);

Quoted 3 lines

- ? ? ? ? ? ? ? ath_wake_mac80211_queue(sc, txq);
+ ? ? ? ? ? ? ? if (txq == sc->tx.txq_map[qnum])
+ ? ? ? ? ? ? ? ? ? ? ? ath_wake_mac80211_queue(sc, qnum);

Out of bounds?

Quoted 19 lines

? ? ? ? ? ? ? ?spin_lock_bh(&txq->axq_lock);
? ? ? ? ? ? ? ?if (!list_empty(&txq->txq_fifo_pending)) {

drivers/net/wireless/ath/ath9k/xmit.c +2 -2
@@ -2375,7 +2366,7 @@ void ath_tx_node_init(struct ath_softc *
 ? ? ? ?for (acno = 0, ac = &an->ac[acno];
 ? ? ? ? ? ? acno < WME_NUM_AC; acno++, ac++) {
 ? ? ? ? ? ? ? ?ac->sched ? ?= false;
- ? ? ? ? ? ? ? ac->qnum = sc->tx.hwq_map[acno];
+ ? ? ? ? ? ? ? ac->txq = sc->tx.txq_map[acno];
 ? ? ? ? ? ? ? ?INIT_LIST_HEAD(&ac->tid_q);
 ? ? ? ?}
 ?}
@@ -2385,17 +2376,13 @@ void ath_tx_node_cleanup(struct ath_soft
 ? ? ? ?struct ath_atx_ac *ac;
 ? ? ? ?struct ath_atx_tid *tid;
 ? ? ? ?struct ath_txq *txq;
- ? ? ? int i, tidno;
+ ? ? ? int tidno;
 

drivers/net/wireless/ath/ath9k/xmit.c void ath_tx_node_cleanup(struct ath_soft · line 2385

Quoted 10 lines
drivers/net/wireless/ath/ath9k/xmit.c +1 -5
 ? ? ? ?for (tidno = 0, tid = &an->tid[tidno];
 ? ? ? ? ? ? tidno < WME_NUM_TID; tidno++, tid++) {
- ? ? ? ? ? ? ? i = tid->ac->qnum;
-
- ? ? ? ? ? ? ? if (!ATH_TXQ_SETUP(sc, i))
- ? ? ? ? ? ? ? ? ? ? ? continue;
 
- ? ? ? ? ? ? ? txq = &sc->tx.txq[i];
 ? ? ? ? ? ? ? ?ac = tid->ac;
+ ? ? ? ? ? ? ? txq = ac->txq;

This is where it gets interesting... Since we do select the tid by looking at the header qos and the tid maps to an ac, we implicitly select the txq by looking at the header qos, no?

This means that when we get to ath_tx_start_dma() we lock the txq selected by looking at the skb queue mapping (i.e. txctl->txq), but we then procede into ath_tx_send_ampdu() where the packet is queued to a tid selected by looking at the header qos field. Later that packet will be transmitted on the txq corresponding to that tid (tid ->ac ->txq).

It comes down to this: either we look at the header qos when we select the queue (so the above cannot happen) or we relay on mac80211 to set the header qos and the skb queue mapping in a certain way. If we choose the later I vote for a BUG_ON(txctl->txq != tid->ac->txq) in ath_tx_send_ampdu().

Quoted 101 lines
drivers/net/wireless/ath/ath9k/xmit.c +0 -0
 ? ? ? ? ? ? ? ?spin_lock_bh(&txq->axq_lock);
 
drivers/net/wireless/ath/ath9k/hw.h +0 -0
@@ -157,6 +157,13 @@

?#define PAPRD_GAIN_TABLE_ENTRIES ? ?32
?#define PAPRD_TABLE_SZ ? ? ? ? ? ? ?24

drivers/net/wireless/ath/ath9k/hw.h +7 -0
+enum ath_hw_txq_subtype {
+ ? ? ? ATH_TXQ_AC_BE = 0,
+ ? ? ? ATH_TXQ_AC_BK = 1,
+ ? ? ? ATH_TXQ_AC_VI = 2,
+ ? ? ? ATH_TXQ_AC_VO = 3,
+};
+

?enum ath_ini_subsys {
? ? ? ?ATH_INI_PRE = 0,
? ? ? ?ATH_INI_CORE,

drivers/net/wireless/ath/ath9k/htc_drv_txrx.c +0 -0
@@ -20,8 +20,15 @@

?/* TX */
?/******/

drivers/net/wireless/ath/ath9k/htc_drv_txrx.c +7 -0
+static const int subtype_txq_to_hwq[] = {
+ ? ? ? [WME_AC_BE] = ATH_TXQ_AC_BE,
+ ? ? ? [WME_AC_BK] = ATH_TXQ_AC_BK,
+ ? ? ? [WME_AC_VI] = ATH_TXQ_AC_VI,
+ ? ? ? [WME_AC_VO] = ATH_TXQ_AC_VO,
+};
+

?#define ATH9K_HTC_INIT_TXQ(subtype) do { ? ? ? ? ? ? ? ? ? ? ? \
- ? ? ? ? ? ? ? qi.tqi_subtype = subtype; ? ? ? ? ? ? ? ? ? ? ? \
+ ? ? ? ? ? ? ? qi.tqi_subtype = subtype_txq_to_hwq[subtype]; ? \
? ? ? ? ? ? ? ?qi.tqi_aifs = ATH9K_TXQ_USEDEFAULT; ? ? ? ? ? ? \
? ? ? ? ? ? ? ?qi.tqi_cwmin = ATH9K_TXQ_USEDEFAULT; ? ? ? ? ? ?\
? ? ? ? ? ? ? ?qi.tqi_cwmax = ATH9K_TXQ_USEDEFAULT; ? ? ? ? ? ?\

drivers/net/wireless/ath/ath9k/init.c +2 -1
@@ -396,7 +396,8 @@ static void ath9k_init_crypto(struct ath
 
 ?static int ath9k_init_btcoex(struct ath_softc *sc)
 ?{
- ? ? ? int r, qnum;
+ ? ? ? struct ath_txq *txq;
+ ? ? ? int r;
 
 ? ? ? ?switch (sc->sc_ah->btcoex_hw.scheme) {

? ? ? ?case ATH_BTCOEX_CFG_NONE:

drivers/net/wireless/ath/ath9k/init.c +2 -2
@@ -409,8 +410,8 @@ static int ath9k_init_btcoex(struct ath_
 ? ? ? ? ? ? ? ?r = ath_init_btcoex_timer(sc);
 ? ? ? ? ? ? ? ?if (r)
 ? ? ? ? ? ? ? ? ? ? ? ?return -1;
- ? ? ? ? ? ? ? qnum = sc->tx.hwq_map[WME_AC_BE];
- ? ? ? ? ? ? ? ath9k_hw_init_btcoex_hw(sc->sc_ah, qnum);
+ ? ? ? ? ? ? ? txq = sc->tx.txq_map[WME_AC_BE];
+ ? ? ? ? ? ? ? ath9k_hw_init_btcoex_hw(sc->sc_ah, txq->axq_qnum);
 ? ? ? ? ? ? ? ?sc->btcoex.bt_stomp_type = ATH_BTCOEX_STOMP_LOW;
 ? ? ? ? ? ? ? ?break;

? ? ? ?default:

drivers/net/wireless/ath/ath9k/init.c +0 -28
@@ -423,59 +424,18 @@ static int ath9k_init_btcoex(struct ath_
 
 ?static int ath9k_init_queues(struct ath_softc *sc)
 ?{
- ? ? ? struct ath_common *common = ath9k_hw_common(sc->sc_ah);
 ? ? ? ?int i = 0;
 
- ? ? ? for (i = 0; i < ARRAY_SIZE(sc->tx.hwq_map); i++)
- ? ? ? ? ? ? ? sc->tx.hwq_map[i] = -1;
-
 ? ? ? ?sc->beacon.beaconq = ath9k_hw_beaconq_setup(sc->sc_ah);
- ? ? ? if (sc->beacon.beaconq == -1) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup a beacon xmit queue\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
-
 ? ? ? ?sc->beacon.cabq = ath_txq_setup(sc, ATH9K_TX_QUEUE_CAB, 0);
- ? ? ? if (sc->beacon.cabq == NULL) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup CAB xmit queue\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
 
 ? ? ? ?sc->config.cabqReadytime = ATH_CABQ_READY_TIME;
 ? ? ? ?ath_cabq_update(sc);
 
- ? ? ? if (!ath_tx_setup(sc, WME_AC_BK)) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup xmit queue for BK traffic\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
-
- ? ? ? if (!ath_tx_setup(sc, WME_AC_BE)) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup xmit queue for BE traffic\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
- ? ? ? if (!ath_tx_setup(sc, WME_AC_VI)) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,

drivers/net/wireless/ath/ath9k/init.c static int ath9k_init_btcoex(struct ath_ · line 436

Quoted 10 lines
drivers/net/wireless/ath/ath9k/init.c +2 -8
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup xmit queue for VI traffic\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
- ? ? ? if (!ath_tx_setup(sc, WME_AC_VO)) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup xmit queue for VO traffic\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
+ ? ? ? for (i = 0; i < WME_NUM_AC; i++)
+ ? ? ? ? ? ? ? sc->tx.txq_map[i] = ath_txq_setup(sc, ATH9K_TX_QUEUE_DATA, i);

Can we be sure that ath_txq_setup() will always return a distinct txq on each call? Otherwise I suggest an inner loop of BUG_ON() to make sure no two elements of txq_map are the same.

Quoted 91 lines
drivers/net/wireless/ath/ath9k/init.c +0 -7
 ? ? ? ?return 0;
-
-err:
- ? ? ? for (i = 0; i < ATH9K_NUM_TX_QUEUES; i++)
- ? ? ? ? ? ? ? if (ATH_TXQ_SETUP(sc, i))
- ? ? ? ? ? ? ? ? ? ? ? ath_tx_cleanupq(sc, &sc->tx.txq[i]);
-
- ? ? ? return -EIO;
 ?}
 
 ?static int ath9k_init_channels_rates(struct ath_softc *sc)
drivers/net/wireless/ath/ath9k/virtual.c +1 -1
@@ -187,7 +187,7 @@ static int ath9k_send_nullfunc(struct at
 ? ? ? ?info->control.rates[1].idx = -1;
 
 ? ? ? ?memset(&txctl, 0, sizeof(struct ath_tx_control));
- ? ? ? txctl.txq = &sc->tx.txq[sc->tx.hwq_map[WME_AC_VO]];
+ ? ? ? txctl.txq = sc->tx.txq_map[WME_AC_VO];
 ? ? ? ?txctl.frame_type = ps ? ATH9K_IFT_PAUSE : ATH9K_IFT_UNPAUSE;
 
 ? ? ? ?if (ath_tx_start(aphy->hw, skb, &txctl) != 0)
drivers/net/wireless/ath/ath9k/debug.c +11 -9
@@ -579,10 +579,10 @@ static const struct file_operations fops
 ? ? ? ?do { ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?\
 ? ? ? ? ? ? ? ?len += snprintf(buf + len, size - len, ? ? ? ? ? ? ? ? ?\
 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?"%s%13u%11u%10u%10u\n", str, ? ? ? ? ? ?\
- ? ? ? ? ? ? ? sc->debug.stats.txstats[sc->tx.hwq_map[WME_AC_BE]].elem, \
- ? ? ? ? ? ? ? sc->debug.stats.txstats[sc->tx.hwq_map[WME_AC_BK]].elem, \
- ? ? ? ? ? ? ? sc->debug.stats.txstats[sc->tx.hwq_map[WME_AC_VI]].elem, \
- ? ? ? ? ? ? ? sc->debug.stats.txstats[sc->tx.hwq_map[WME_AC_VO]].elem); \
+ ? ? ? ? ? ? ? sc->debug.stats.txstats[WME_AC_BE].elem, \
+ ? ? ? ? ? ? ? sc->debug.stats.txstats[WME_AC_BK].elem, \
+ ? ? ? ? ? ? ? sc->debug.stats.txstats[WME_AC_VI].elem, \
+ ? ? ? ? ? ? ? sc->debug.stats.txstats[WME_AC_VO].elem); \
 ?} while(0)
 
 ?static ssize_t read_file_xmit(struct file *file, char __user *user_buf,
@@ -624,33 +624,35 @@ static ssize_t read_file_xmit(struct fil
 ? ? ? ?return retval;
 ?}
 
-void ath_debug_stat_tx(struct ath_softc *sc, struct ath_txq *txq,
- ? ? ? ? ? ? ? ? ? ? ?struct ath_buf *bf, struct ath_tx_status *ts)
+void ath_debug_stat_tx(struct ath_softc *sc, struct ath_buf *bf,
+ ? ? ? ? ? ? ? ? ? ? ?struct ath_tx_status *ts)
 ?{
- ? ? ? TX_STAT_INC(txq->axq_qnum, tx_pkts_all);
- ? ? ? sc->debug.stats.txstats[txq->axq_qnum].tx_bytes_all += bf->bf_mpdu->len;
+ ? ? ? int qnum = skb_get_queue_mapping(bf->bf_mpdu);
+
+ ? ? ? TX_STAT_INC(qnum, tx_pkts_all);
+ ? ? ? sc->debug.stats.txstats[qnum].tx_bytes_all += bf->bf_mpdu->len;
 
 ? ? ? ?if (bf_isampdu(bf)) {
 ? ? ? ? ? ? ? ?if (bf_isxretried(bf))
- ? ? ? ? ? ? ? ? ? ? ? TX_STAT_INC(txq->axq_qnum, a_xretries);
+ ? ? ? ? ? ? ? ? ? ? ? TX_STAT_INC(qnum, a_xretries);

? ? ? ? ? ? ? ?else
- ? ? ? ? ? ? ? ? ? ? ? TX_STAT_INC(txq->axq_qnum, a_completed);
+ ? ? ? ? ? ? ? ? ? ? ? TX_STAT_INC(qnum, a_completed); ? ? ? ?} else {
- ? ? ? ? ? ? ? TX_STAT_INC(txq->axq_qnum, completed);
+ ? ? ? ? ? ? ? TX_STAT_INC(qnum, completed);
? ? ? ?}

? ? ? ?if (ts->ts_status & ATH9K_TXERR_FIFO)
- ? ? ? ? ? ? ? TX_STAT_INC(txq->axq_qnum, fifo_underrun);
+ ? ? ? ? ? ? ? TX_STAT_INC(qnum, fifo_underrun); ? ? ? ?if (ts->ts_status & ATH9K_TXERR_XTXOP)
- ? ? ? ? ? ? ? TX_STAT_INC(txq->axq_qnum, xtxop);
+ ? ? ? ? ? ? ? TX_STAT_INC(qnum, xtxop);
? ? ? ?if (ts->ts_status & ATH9K_TXERR_TIMER_EXPIRED)
- ? ? ? ? ? ? ? TX_STAT_INC(txq->axq_qnum, timer_exp);
+ ? ? ? ? ? ? ? TX_STAT_INC(qnum, timer_exp);
? ? ? ?if (ts->ts_flags & ATH9K_TX_DESC_CFG_ERR)
- ? ? ? ? ? ? ? TX_STAT_INC(txq->axq_qnum, desc_cfg_err);
+ ? ? ? ? ? ? ? TX_STAT_INC(qnum, desc_cfg_err);
? ? ? ?if (ts->ts_flags & ATH9K_TX_DATA_UNDERRUN)
- ? ? ? ? ? ? ? TX_STAT_INC(txq->axq_qnum, data_underrun);
+ ? ? ? ? ? ? ? TX_STAT_INC(qnum, data_underrun); ? ? ? ?if (ts->ts_flags & ATH9K_TX_DELIM_UNDERRUN)
- ? ? ? ? ? ? ? TX_STAT_INC(txq->axq_qnum, delim_underrun);
+ ? ? ? ? ? ? ? TX_STAT_INC(qnum, delim_underrun); ?}

?static const struct file_operations fops_xmit = {

#8 lore raw
Quoted 24 lines · Bj?rn Smedman

This is one good looking patch. :) And I agree, looking at the header qos is good to avoid.

But there is still the risk of queue selection mismatch as I see it... See comments below.

/Bj?rn

Quoted 16 lines
drivers/net/wireless/ath/ath9k/main.c +0 -2
-
 /* XXX: Remove me once we don't depend on ath9k_channel for all
 * this redundant data */
 void ath9k_update_ichannel(struct ath_softc *sc, struct ieee80211_hw *hw,
@@ -1244,7 +1193,6 @@ static int ath9k_tx(struct ieee80211_hw
       struct ath_tx_control txctl;
       int padpos, padsize;
       struct ieee80211_hdr *hdr = (struct ieee80211_hdr *) skb->data;
-       int qnum;
 
       if (aphy->state != ATH_WIPHY_ACTIVE && aphy->state != ATH_WIPHY_SCAN) {
               ath_print(common, ATH_DBG_XMIT,
@@ -1317,8 +1265,7 @@ static int ath9k_tx(struct ieee80211_hw
               memmove(skb->data, skb->data + padsize, padpos);
       }
 
Quoted 9 lines

drivers/net/wireless/ath/ath9k/main.c static int ath9k_tx(struct ieee80211_hw · line 1268

Quoted 3 lines
drivers/net/wireless/ath/ath9k/main.c +1 -2
-       qnum = ath_get_hal_qnum(skb_get_queue_mapping(skb), sc);
-       txctl.txq = &sc->tx.txq[qnum];
+       txctl.txq = sc->tx.txq_map[skb_get_queue_mapping(skb)];

Could we be indexing txq_map[] out of bounds here? I guess this question is the fundamental one: can we be sure that skb_get_queue_mapping(skb) will return an AC i.e. range 0-3? Not only now but forever? Or do we need a comment in mac80211 saying driver will crash if anything else is returned?

mac80211 already makes the same assumption in several places. It should never be out of bounds unless something in the network stack is broken. And if there is a need for a defensive check for this, then ath9k is definitely not the right place for it.

Quoted 5 lines
Quoted 5 lines
drivers/net/wireless/ath/ath9k/xmit.c +0 -1
@@ -1756,8 +1744,9 @@ int ath_tx_start(struct ieee80211_hw *hw
                * we will at least have to run TX completionon one buffer
                * on the queue */
               spin_lock_bh(&txq->axq_lock);
-               if (!txq->stopped && txq->axq_depth > 1) {
Quoted 8 lines

drivers/net/wireless/ath/ath9k/xmit.c int ath_tx_start(struct ieee80211_hw *hw · line 1749

Quoted 4 lines
drivers/net/wireless/ath/ath9k/xmit.c +3 -1
-                       ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+               if (txq == sc->tx.txq_map[q] && !txq->stopped &&
+                   txq->axq_depth > 1) {
+                       ath_mac80211_stop_queue(sc, q);

Again, possible index out of bounds, no? Also, what happens if txq != sc->tx.txq_map[q]? I guess that's less catastrophic but still; meaningful code will not execute.

I added that check primarily for the case where buffered frames go through the cabq.

Quoted 32 lines
Quoted 7 lines
drivers/net/wireless/ath/ath9k/xmit.c +0 -0
                       txq->stopped = 1;
               }
               spin_unlock_bh(&txq->axq_lock);
@@ -1767,13 +1756,10 @@ int ath_tx_start(struct ieee80211_hw *hw
               return r;
       }
 

drivers/net/wireless/ath/ath9k/xmit.c int ath_tx_start(struct ieee80211_hw *hw · line 1762

Quoted 10 lines
drivers/net/wireless/ath/ath9k/xmit.c +3 -6
-       q = skb_get_queue_mapping(skb);
-       if (q >= 4)
-               q = 0;
-
       spin_lock_bh(&txq->axq_lock);
-       if (++sc->tx.pending_frames[q] > ATH_MAX_QDEPTH && !txq->stopped) {
-               ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+       if (txq == sc->tx.txq_map[q] &&
+           ++txq->pending_frames > ATH_MAX_QDEPTH && !txq->stopped) {
+               ath_mac80211_stop_queue(sc, q);

Same as above.

Quoted 12 lines
drivers/net/wireless/ath/ath9k/xmit.c +1 -3
               txq->stopped = 1;
       }
       spin_unlock_bh(&txq->axq_lock);
@@ -1887,12 +1873,12 @@ static void ath_tx_complete(struct ath_s
       if (unlikely(tx_info->pad[0] & ATH_TX_INFO_FRAME_TYPE_INTERNAL))
               ath9k_tx_status(hw, skb);
       else {
-               q = skb_get_queue_mapping(skb);
-               if (q >= 4)
-                       q = 0;
+               struct ath_txq *txq;
 
Quoted 9 lines

drivers/net/wireless/ath/ath9k/xmit.c static void ath_tx_complete(struct ath_s · line 1881

Quoted 6 lines
drivers/net/wireless/ath/ath9k/xmit.c +4 -2
-               if (--sc->tx.pending_frames[q] < 0)
-                       sc->tx.pending_frames[q] = 0;
+               q = skb_get_queue_mapping(skb);
+               txq = sc->tx.txq_map[q];
+               if (--txq->pending_frames < 0)
+                       txq->pending_frames = 0;

This is off topic, cut do we really need this? Where do those missing frames go? :) I would much prefer a BUG_ON(txq->pending_frames < 0).

BUG_ON is not a good idea, it's only supposed to be used for cases with potentially severe side effects, things like random memory corruption. A counting imbalance here would be completely harmless, so@most we should have a WARN_ON_ONCE here.

Quoted 40 lines
Quoted 18 lines
drivers/net/wireless/ath/ath9k/xmit.c +2 -2
               spin_lock_bh(&txq->axq_lock);
               if (!list_empty(&txq->txq_fifo_pending)) {
@@ -2375,7 +2366,7 @@ void ath_tx_node_init(struct ath_softc *
       for (acno = 0, ac = &an->ac[acno];
            acno < WME_NUM_AC; acno++, ac++) {
               ac->sched    = false;
-               ac->qnum = sc->tx.hwq_map[acno];
+               ac->txq = sc->tx.txq_map[acno];
               INIT_LIST_HEAD(&ac->tid_q);
       }
 }
@@ -2385,17 +2376,13 @@ void ath_tx_node_cleanup(struct ath_soft
       struct ath_atx_ac *ac;
       struct ath_atx_tid *tid;
       struct ath_txq *txq;
-       int i, tidno;
+       int tidno;
 

drivers/net/wireless/ath/ath9k/xmit.c void ath_tx_node_cleanup(struct ath_soft · line 2385

Quoted 10 lines
drivers/net/wireless/ath/ath9k/xmit.c +1 -5
       for (tidno = 0, tid = &an->tid[tidno];
            tidno < WME_NUM_TID; tidno++, tid++) {
-               i = tid->ac->qnum;
-
-               if (!ATH_TXQ_SETUP(sc, i))
-                       continue;
 
-               txq = &sc->tx.txq[i];
               ac = tid->ac;
+               txq = ac->txq;

This is where it gets interesting... Since we do select the tid by looking at the header qos and the tid maps to an ac, we implicitly select the txq by looking at the header qos, no?

This means that when we get to ath_tx_start_dma() we lock the txq selected by looking at the skb queue mapping (i.e. txctl->txq), but we then procede into ath_tx_send_ampdu() where the packet is queued to a tid selected by looking at the header qos field. Later that packet will be transmitted on the txq corresponding to that tid (tid ->ac ->txq).

Quoted 5 lines

It comes down to this: either we look at the header qos when we select the queue (so the above cannot happen) or we relay on mac80211 to set the header qos and the skb queue mapping in a certain way. If we choose the later I vote for a BUG_ON(txctl->txq != tid->ac->txq) in ath_tx_send_ampdu().

For regular QoS data frames (and no other frames ever hit the aggregation code) there is only one possible way to map tid -> ac -> queue. I did review those code paths, and I believe them to be safe. If you want, we can add a WARN_ON_ONCE later, but definitely no BUG_ON.

Quoted 46 lines
Quoted 46 lines
drivers/net/wireless/ath/ath9k/init.c +0 -34
@@ -423,59 +424,18 @@ static int ath9k_init_btcoex(struct ath_
 
 static int ath9k_init_queues(struct ath_softc *sc)
 {
-       struct ath_common *common = ath9k_hw_common(sc->sc_ah);
       int i = 0;
 
-       for (i = 0; i < ARRAY_SIZE(sc->tx.hwq_map); i++)
-               sc->tx.hwq_map[i] = -1;
-
       sc->beacon.beaconq = ath9k_hw_beaconq_setup(sc->sc_ah);
-       if (sc->beacon.beaconq == -1) {
-               ath_print(common, ATH_DBG_FATAL,
-                         "Unable to setup a beacon xmit queue\n");
-               goto err;
-       }
-
       sc->beacon.cabq = ath_txq_setup(sc, ATH9K_TX_QUEUE_CAB, 0);
-       if (sc->beacon.cabq == NULL) {
-               ath_print(common, ATH_DBG_FATAL,
-                         "Unable to setup CAB xmit queue\n");
-               goto err;
-       }
 
       sc->config.cabqReadytime = ATH_CABQ_READY_TIME;
       ath_cabq_update(sc);
 
-       if (!ath_tx_setup(sc, WME_AC_BK)) {
-               ath_print(common, ATH_DBG_FATAL,
-                         "Unable to setup xmit queue for BK traffic\n");
-               goto err;
-       }
-
-       if (!ath_tx_setup(sc, WME_AC_BE)) {
-               ath_print(common, ATH_DBG_FATAL,
-                         "Unable to setup xmit queue for BE traffic\n");
-               goto err;
-       }
-       if (!ath_tx_setup(sc, WME_AC_VI)) {
-               ath_print(common, ATH_DBG_FATAL,
-                         "Unable to setup xmit queue for VI traffic\n");
-               goto err;
-       }
-       if (!ath_tx_setup(sc, WME_AC_VO)) {
-               ath_print(common, ATH_DBG_FATAL,
-                         "Unable to setup xmit queue for VO traffic\n");
Quoted 8 lines

drivers/net/wireless/ath/ath9k/init.c static int ath9k_init_btcoex(struct ath_ · line 436

Quoted 4 lines
drivers/net/wireless/ath/ath9k/init.c +2 -2
-               goto err;
-       }
+       for (i = 0; i < WME_NUM_AC; i++)
+               sc->tx.txq_map[i] = ath_txq_setup(sc, ATH9K_TX_QUEUE_DATA, i);

Can we be sure that ath_txq_setup() will always return a distinct txq on each call? Otherwise I suggest an inner loop of BUG_ON() to make sure no two elements of txq_map are the same.

Yes, we can be sure. I reviewed the entire code path that this runs through and there is no way that this can fail. There are way too many layers of useless defensive code in ath9k, and I think we should start getting rid of them one by one ;)

- Felix

#9 lore raw

2010/11/3 Felix Fietkau <[email protected]>:

Quoted 34 lines · Bj?rn Smedman
Quoted 24 lines

This is one good looking patch. :) And I agree, looking at the header qos is good to avoid.

But there is still the risk of queue selection mismatch as I see it... See comments below.

/Bj?rn

Quoted 16 lines

-
?/* XXX: Remove me once we don't depend on ath9k_channel for all ?* this redundant data */
?void ath9k_update_ichannel(struct ath_softc *sc, struct ieee80211_hw *hw,

(quoted diff) +0 -1
@@ -1244,7 +1193,6 @@ static int ath9k_tx(struct ieee80211_hw
 ? ? ? ?struct ath_tx_control txctl;
 ? ? ? ?int padpos, padsize;
 ? ? ? ?struct ieee80211_hdr *hdr = (struct ieee80211_hdr *) skb->data;
- ? ? ? int qnum;
 
 ? ? ? ?if (aphy->state != ATH_WIPHY_ACTIVE && aphy->state != ATH_WIPHY_SCAN) {
 ? ? ? ? ? ? ? ?ath_print(common, ATH_DBG_XMIT,
@@ -1317,8 +1265,7 @@ static int ath9k_tx(struct ieee80211_hw
 ? ? ? ? ? ? ? ?memmove(skb->data, skb->data + padsize, padpos);
 ? ? ? ?}
 
Quoted 9 lines

Review static int ath9k_tx(struct ieee80211_hw · line 1268

Quoted 3 lines
(quoted diff) +1 -2
- ? ? ? qnum = ath_get_hal_qnum(skb_get_queue_mapping(skb), sc);
- ? ? ? txctl.txq = &sc->tx.txq[qnum];
+ ? ? ? txctl.txq = sc->tx.txq_map[skb_get_queue_mapping(skb)];

Could we be indexing txq_map[] out of bounds here? I guess this question is the fundamental one: can we be sure that skb_get_queue_mapping(skb) will return an AC i.e. range 0-3? Not only now but forever? Or do we need a comment in mac80211 saying driver will crash if anything else is returned?

Quoted 4 lines

mac80211 already makes the same assumption in several places. It should never be out of bounds unless something in the network stack is broken. And if there is a need for a defensive check for this, then ath9k is definitely not the right place for it.

Okej, if that is the stable contract I'm ok with it.

Quoted 13 lines
Quoted 5 lines
Quoted 5 lines
(quoted diff) +0 -0
@@ -1756,8 +1744,9 @@ int ath_tx_start(struct ieee80211_hw *hw

? ? ? ? ? ? ? ? * we will at least have to run TX completionon one buffer ? ? ? ? ? ? ? ? * on the queue */
? ? ? ? ? ? ? ?spin_lock_bh(&txq->axq_lock);
- ? ? ? ? ? ? ? if (!txq->stopped && txq->axq_depth > 1) {

Quoted 8 lines
Quoted 4 lines

- ? ? ? ? ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+ ? ? ? ? ? ? ? if (txq == sc->tx.txq_map[q] && !txq->stopped &&
+ ? ? ? ? ? ? ? ? ? txq->axq_depth > 1) {
+ ? ? ? ? ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, q);

Again, possible index out of bounds, no? Also, what happens if txq != sc->tx.txq_map[q]? I guess that's less catastrophic but still; meaningful code will not execute.

Quoted 2 lines

I added that check primarily for the case where buffered frames go through the cabq.

Ok, if there is no other case then sure.

Quoted 42 lines
Quoted 33 lines
Quoted 8 lines

? ? ? ? ? ? ? ? ? ? ? ?txq->stopped = 1;
? ? ? ? ? ? ? ?}
? ? ? ? ? ? ? ?spin_unlock_bh(&txq->axq_lock);

(quoted diff) +0 -0
@@ -1767,13 +1756,10 @@ int ath_tx_start(struct ieee80211_hw *hw
 ? ? ? ? ? ? ? ?return r;
 ? ? ? ?}
 

Review int ath_tx_start(struct ieee80211_hw *hw · line 1762

Quoted 10 lines
(quoted diff) +3 -6
- ? ? ? q = skb_get_queue_mapping(skb);
- ? ? ? if (q >= 4)
- ? ? ? ? ? ? ? q = 0;
-
 ? ? ? ?spin_lock_bh(&txq->axq_lock);
- ? ? ? if (++sc->tx.pending_frames[q] > ATH_MAX_QDEPTH && !txq->stopped) {
- ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, skb_get_queue_mapping(skb));
+ ? ? ? if (txq == sc->tx.txq_map[q] &&
+ ? ? ? ? ? ++txq->pending_frames > ATH_MAX_QDEPTH && !txq->stopped) {
+ ? ? ? ? ? ? ? ath_mac80211_stop_queue(sc, q);

Same as above.

Quoted 12 lines
(quoted diff) +1 -3
 ? ? ? ? ? ? ? ?txq->stopped = 1;
 ? ? ? ?}
 ? ? ? ?spin_unlock_bh(&txq->axq_lock);
@@ -1887,12 +1873,12 @@ static void ath_tx_complete(struct ath_s
 ? ? ? ?if (unlikely(tx_info->pad[0] & ATH_TX_INFO_FRAME_TYPE_INTERNAL))
 ? ? ? ? ? ? ? ?ath9k_tx_status(hw, skb);
 ? ? ? ?else {
- ? ? ? ? ? ? ? q = skb_get_queue_mapping(skb);
- ? ? ? ? ? ? ? if (q >= 4)
- ? ? ? ? ? ? ? ? ? ? ? q = 0;
+ ? ? ? ? ? ? ? struct ath_txq *txq;
 
Quoted 9 lines

Review static void ath_tx_complete(struct ath_s · line 1881

Quoted 6 lines
(quoted diff) +4 -2
- ? ? ? ? ? ? ? if (--sc->tx.pending_frames[q] < 0)
- ? ? ? ? ? ? ? ? ? ? ? sc->tx.pending_frames[q] = 0;
+ ? ? ? ? ? ? ? q = skb_get_queue_mapping(skb);
+ ? ? ? ? ? ? ? txq = sc->tx.txq_map[q];
+ ? ? ? ? ? ? ? if (--txq->pending_frames < 0)
+ ? ? ? ? ? ? ? ? ? ? ? txq->pending_frames = 0;

This is off topic, cut do we really need this? Where do those missing frames go? :) I would much prefer a BUG_ON(txq->pending_frames < 0).

Quoted 4 lines

BUG_ON is not a good idea, it's only supposed to be used for cases with potentially severe side effects, things like random memory corruption. A counting imbalance here would be completely harmless, so at most we should have a WARN_ON_ONCE here.

Ok, agree.

Quoted 46 lines
Quoted 41 lines
Quoted 19 lines
(quoted diff) +2 -2
 ? ? ? ? ? ? ? ?spin_lock_bh(&txq->axq_lock);
 ? ? ? ? ? ? ? ?if (!list_empty(&txq->txq_fifo_pending)) {
@@ -2375,7 +2366,7 @@ void ath_tx_node_init(struct ath_softc *
 ? ? ? ?for (acno = 0, ac = &an->ac[acno];
 ? ? ? ? ? ? acno < WME_NUM_AC; acno++, ac++) {
 ? ? ? ? ? ? ? ?ac->sched ? ?= false;
- ? ? ? ? ? ? ? ac->qnum = sc->tx.hwq_map[acno];
+ ? ? ? ? ? ? ? ac->txq = sc->tx.txq_map[acno];
 ? ? ? ? ? ? ? ?INIT_LIST_HEAD(&ac->tid_q);
 ? ? ? ?}
 ?}
@@ -2385,17 +2376,13 @@ void ath_tx_node_cleanup(struct ath_soft
 ? ? ? ?struct ath_atx_ac *ac;
 ? ? ? ?struct ath_atx_tid *tid;
 ? ? ? ?struct ath_txq *txq;
- ? ? ? int i, tidno;
+ ? ? ? int tidno;
 

Review void ath_tx_node_cleanup(struct ath_soft · line 2385

Quoted 10 lines
(quoted diff) +1 -5
 ? ? ? ?for (tidno = 0, tid = &an->tid[tidno];
 ? ? ? ? ? ? tidno < WME_NUM_TID; tidno++, tid++) {
- ? ? ? ? ? ? ? i = tid->ac->qnum;
-
- ? ? ? ? ? ? ? if (!ATH_TXQ_SETUP(sc, i))
- ? ? ? ? ? ? ? ? ? ? ? continue;
 
- ? ? ? ? ? ? ? txq = &sc->tx.txq[i];
 ? ? ? ? ? ? ? ?ac = tid->ac;
+ ? ? ? ? ? ? ? txq = ac->txq;

This is where it gets interesting... Since we do select the tid by looking at the header qos and the tid maps to an ac, we implicitly select the txq by looking at the header qos, no?

This means that when we get to ath_tx_start_dma() we lock the txq selected by looking at the skb queue mapping (i.e. txctl->txq), but we then procede into ath_tx_send_ampdu() where the packet is queued to a tid selected by looking at the header qos field. Later that packet will be transmitted on the txq corresponding to that tid (tid ->ac ->txq).

Quoted 5 lines

It comes down to this: either we look at the header qos when we select the queue (so the above cannot happen) or we relay on mac80211 to set the header qos and the skb queue mapping in a certain way. If we choose the later I vote for a BUG_ON(txctl->txq != tid->ac->txq) in ath_tx_send_ampdu().

Quoted 4 lines

For regular QoS data frames (and no other frames ever hit the aggregation code) there is only one possible way to map tid -> ac -> queue. I did review those code paths, and I believe them to be safe. If you want, we can add a WARN_ON_ONCE later, but definitely no BUG_ON.

I've briefly looked through the IEEE Std 802.11e-2005. There is a clear requirement that "There shall be no reordering of unicast MSDUs with the same TID value and addressed to the same destination" in analog to what Hulmut pointed out earlier. Other than that the only reference I can find is that: "The MAC data service for QSTAs shall incorporate a TID with each MA-UNITDATA.request service. This TID associates the MSDU with the AC or TS queue for the indicated traffic." Why are you sure there is only one way to map tid -> ac -> queue? I don't think it's hard to come up with a case where you want to map differently (e.g. depending on RA or even TA).

Ok, regardless. So lets say there is a bug in mac80211 that allows a "mismatch" between header qos tid and skb queue mapping to occur (which in fact there is because this happens all the time with my frame injection heavy app). Then it's ok for ath9k to screw up the locking, possibly corrupt data and so on, silently?

Other than that I guess that it's basically an argument about aesthetics, and you may very well be right. All I know is that I've been following ath9k development now for almost two years and I'm amazed by the severity of bugs that are still found, and I guess yet to be found. We're dma:ing all over the place, deadlocking queues and so on, on a regular basis, or at least we where 3 months ago. After each one of these is fixed the attitude seems to be "now everything is perfect and suggesting there could be some more problems or will be in the future is just plain rude". Then yet another is found...

If you relay on something so fragile as the contents of frame data "matching" skb_get_queue_mapping() I think you owe me at least a WARN_ON_ONCE before you start corrupting memory. ;)

Quoted 54 lines
Quoted 46 lines
Quoted 46 lines
(quoted diff) +0 -34
@@ -423,59 +424,18 @@ static int ath9k_init_btcoex(struct ath_
 
 ?static int ath9k_init_queues(struct ath_softc *sc)
 ?{
- ? ? ? struct ath_common *common = ath9k_hw_common(sc->sc_ah);
 ? ? ? ?int i = 0;
 
- ? ? ? for (i = 0; i < ARRAY_SIZE(sc->tx.hwq_map); i++)
- ? ? ? ? ? ? ? sc->tx.hwq_map[i] = -1;
-
 ? ? ? ?sc->beacon.beaconq = ath9k_hw_beaconq_setup(sc->sc_ah);
- ? ? ? if (sc->beacon.beaconq == -1) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup a beacon xmit queue\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
-
 ? ? ? ?sc->beacon.cabq = ath_txq_setup(sc, ATH9K_TX_QUEUE_CAB, 0);
- ? ? ? if (sc->beacon.cabq == NULL) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup CAB xmit queue\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
 
 ? ? ? ?sc->config.cabqReadytime = ATH_CABQ_READY_TIME;
 ? ? ? ?ath_cabq_update(sc);
 
- ? ? ? if (!ath_tx_setup(sc, WME_AC_BK)) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup xmit queue for BK traffic\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
-
- ? ? ? if (!ath_tx_setup(sc, WME_AC_BE)) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup xmit queue for BE traffic\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
- ? ? ? if (!ath_tx_setup(sc, WME_AC_VI)) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup xmit queue for VI traffic\n");
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
- ? ? ? if (!ath_tx_setup(sc, WME_AC_VO)) {
- ? ? ? ? ? ? ? ath_print(common, ATH_DBG_FATAL,
- ? ? ? ? ? ? ? ? ? ? ? ? "Unable to setup xmit queue for VO traffic\n");
Quoted 8 lines

Review static int ath9k_init_btcoex(struct ath_ · line 436

Quoted 4 lines
(quoted diff) +2 -2
- ? ? ? ? ? ? ? goto err;
- ? ? ? }
+ ? ? ? for (i = 0; i < WME_NUM_AC; i++)
+ ? ? ? ? ? ? ? sc->tx.txq_map[i] = ath_txq_setup(sc, ATH9K_TX_QUEUE_DATA, i);

Can we be sure that ath_txq_setup() will always return a distinct txq on each call? Otherwise I suggest an inner loop of BUG_ON() to make sure no two elements of txq_map are the same.

Quoted 4 lines

Yes, we can be sure. I reviewed the entire code path that this runs through and there is no way that this can fail. There are way too many layers of useless defensive code in ath9k, and I think we should start getting rid of them one by one ;)

As long as we agree that is the contract I'm fine with it.

/Bj?rn

#10 lore raw
Quoted 10 lines · Bj?rn Smedman
Quoted 9 lines
Quoted 5 lines

It comes down to this: either we look at the header qos when we select the queue (so the above cannot happen) or we relay on mac80211 to set the header qos and the skb queue mapping in a certain way. If we choose the later I vote for a BUG_ON(txctl->txq != tid->ac->txq) in ath_tx_send_ampdu().

For regular QoS data frames (and no other frames ever hit the aggregation code) there is only one possible way to map tid -> ac -> queue. I did review those code paths, and I believe them to be safe. If you want, we can add a WARN_ON_ONCE later, but definitely no BUG_ON.

Quoted 10 lines

I've briefly looked through the IEEE Std 802.11e-2005. There is a clear requirement that "There shall be no reordering of unicast MSDUs with the same TID value and addressed to the same destination" in analog to what Hulmut pointed out earlier. Other than that the only reference I can find is that: "The MAC data service for QSTAs shall incorporate a TID with each MA-UNITDATA.request service. This TID associates the MSDU with the AC or TS queue for the indicated traffic." Why are you sure there is only one way to map tid -> ac -> queue? I don't think it's hard to come up with a case where you want to map differently (e.g. depending on RA or even TA).

Take a look at Table 9-1 on page 253 (PDF page 301) in 802.11-2007.

Quoted 5 lines

Ok, regardless. So lets say there is a bug in mac80211 that allows a "mismatch" between header qos tid and skb queue mapping to occur (which in fact there is because this happens all the time with my frame injection heavy app). Then it's ok for ath9k to screw up the locking, possibly corrupt data and so on, silently?

I don't see potential for locking issues or data corruption here, even if such a bug were to show up.

Quoted 9 lines

Other than that I guess that it's basically an argument about aesthetics, and you may very well be right. All I know is that I've been following ath9k development now for almost two years and I'm amazed by the severity of bugs that are still found, and I guess yet to be found. We're dma:ing all over the place, deadlocking queues and so on, on a regular basis, or at least we where 3 months ago. After each one of these is fixed the attitude seems to be "now everything is perfect and suggesting there could be some more problems or will be in the future is just plain rude". Then yet another is found...

I'm not saying we should assume that everything is always fine, but I do object to adding defensive code against made up scenarios of potential bugs that "might" be introduced at some point in the future.

Quoted 3 lines

If you relay on something so fragile as the contents of frame data "matching" skb_get_queue_mapping() I think you owe me at least a WARN_ON_ONCE before you start corrupting memory. ;)

The assumption that I make is not just about some random field in the frame contents. I'm assuming that ieee80211_select_queue() makes a sane decision that matches the description in the standard, and that the network stack preserves the decision that this function made. And besides - it's not like part of ath9k that cares about the TID is going to live on for much longer :)

- Felix

#11 lore raw
Quoted 9 lines · Felix Fietkau
Quoted 9 lines

Other than that I guess that it's basically an argument about aesthetics, and you may very well be right. All I know is that I've been following ath9k development now for almost two years and I'm amazed by the severity of bugs that are still found, and I guess yet to be found. We're dma:ing all over the place, deadlocking queues and so on, on a regular basis, or at least we where 3 months ago. After each one of these is fixed the attitude seems to be "now everything is perfect and suggesting there could be some more problems or will be in the future is just plain rude". Then yet another is found...

Quoted 3 lines

I'm not saying we should assume that everything is always fine, but I do object to adding defensive code against made up scenarios of potential bugs that "might" be introduced at some point in the future.

I think a few WARN_ON_ONCE calls might be nice to have..folks changing one part of the network stack often don't realize the subtle dependencies in other parts..and a WARN_ON is a lot easier to debug than random crashes and DMA errors. For anyone reading the code, it is quite obvious that you should never hit the WARN_ON, so I don't think it adds any real clutter.

Thanks,
Ben

Signature · 2 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com
#12 lore raw
In reply to Felix Fietkau

2010/11/3 Felix Fietkau <[email protected]>:

Quoted 8 lines · Bj?rn Smedman
Quoted 5 lines

Ok, regardless. So lets say there is a bug in mac80211 that allows a "mismatch" between header qos tid and skb queue mapping to occur (which in fact there is because this happens all the time with my frame injection heavy app). Then it's ok for ath9k to screw up the locking, possibly corrupt data and so on, silently?

I don't see potential for locking issues or data corruption here, even if such a bug were to show up.

Then I think this is the only point we really disagree on. :)

It goes like this. When we get to ath_tx_start_dma() there already is a txq assigned (passed as txctl->txq) and we lock that txq. Then, if it's aggregation data we look up the tid:

                an = (struct ath_node *)tx_info->control.sta->drv_priv;
                tid = ATH_AN_2_TID(an, bf->bf_tidno);

Notice how bf->bf_tidno is used. This contains the TID from the 802.11 header qos field. That means tid->ac->txq may not be the same as txctl->txq if there is a mismatch between frame data and skb queue mapping. Now we call ath_tx_send_ampdu() which presumes the txq (and therefore the associated tid) is already locked and starts fiddling with e.g. tid->buf_q, in this case without holding tid->ac->txq->axq_lock. This is racy e.g. against ath_draintxq() / ath_txq_drain_pending_buffers() which does not know about this madness and locks the correct txq.

Quoted 3 lines

I'm not saying we should assume that everything is always fine, but I do object to adding defensive code against made up scenarios of potential bugs that "might" be introduced at some point in the future.

I can see your point. I don't want lots of defensive stuff (like what you removed in your patch). But I still feel the balance is wrong. Take one recent case for example: We're not 100% sure we can always stop RX dma. In fact, a few weeks ago we weren't even sure what we didn't start it when we weren't supposed to. Yet for some reason there seems to be a consensus it is a good idea to keep ds_data of all those dma descriptors pointing at arbitrary kernel data. I realize it takes some time and adds some clutter to do "ds_data = 0". I also understand it does not help in all cases. But I think it's a reasonable precaution under the circumstances. It's like in medicine, patients will die but when they do you want to be able to say "we did everything we could". ;)

Quoted 9 lines
Quoted 3 lines

If you relay on something so fragile as the contents of frame data "matching" skb_get_queue_mapping() I think you owe me at least a WARN_ON_ONCE before you start corrupting memory. ;)

The assumption that I make is not just about some random field in the frame contents. I'm assuming that ieee80211_select_queue() makes a sane decision that matches the description in the standard, and that the network stack preserves the decision that this function made. And besides - it's not like part of ath9k that cares about the TID is going to live on for much longer :)

I guess you are talking aggregation in mac80211. Very much looking forward to that. :)

/Bj?rn

#13 lore raw
Quoted 19 lines · Bj?rn Smedman

2010/11/3 Felix Fietkau <[email protected]>:

Quoted 8 lines · Bj?rn Smedman
Quoted 5 lines

Ok, regardless. So lets say there is a bug in mac80211 that allows a "mismatch" between header qos tid and skb queue mapping to occur (which in fact there is because this happens all the time with my frame injection heavy app). Then it's ok for ath9k to screw up the locking, possibly corrupt data and so on, silently?

I don't see potential for locking issues or data corruption here, even if such a bug were to show up.

Then I think this is the only point we really disagree on. :)

It goes like this. When we get to ath_tx_start_dma() there already is a txq assigned (passed as txctl->txq) and we lock that txq. Then, if it's aggregation data we look up the tid:

                an = (struct ath_node *)tx_info->control.sta->drv_priv;
                tid = ATH_AN_2_TID(an, bf->bf_tidno);
Quoted 9 lines

Notice how bf->bf_tidno is used. This contains the TID from the 802.11 header qos field. That means tid->ac->txq may not be the same as txctl->txq if there is a mismatch between frame data and skb queue mapping. Now we call ath_tx_send_ampdu() which presumes the txq (and therefore the associated tid) is already locked and starts fiddling with e.g. tid->buf_q, in this case without holding tid->ac->txq->axq_lock. This is racy e.g. against ath_draintxq() / ath_txq_drain_pending_buffers() which does not know about this madness and locks the correct txq.

Hmm, I guess you have a point there ;)

Quoted 4 lines
Quoted 3 lines

I'm not saying we should assume that everything is always fine, but I do object to adding defensive code against made up scenarios of potential bugs that "might" be introduced at some point in the future.

Quoted 12 lines

I can see your point. I don't want lots of defensive stuff (like what you removed in your patch). But I still feel the balance is wrong. Take one recent case for example: We're not 100% sure we can always stop RX dma. In fact, a few weeks ago we weren't even sure what we didn't start it when we weren't supposed to. Yet for some reason there seems to be a consensus it is a good idea to keep ds_data of all those dma descriptors pointing at arbitrary kernel data. I realize it takes some time and adds some clutter to do "ds_data = 0". I also understand it does not help in all cases. But I think it's a reasonable precaution under the circumstances. It's like in medicine, patients will die but when they do you want to be able to say "we did everything we could". ;)

Actually, when dealing with hardware pointers, I'm not sure setting them to 0 makes things any better, since 0 still points to a physical RAM location :)

- Felix

#14 lore raw
In reply to Felix Fietkau

2010/11/2 Felix Fietkau <[email protected]>:

Quoted 6 lines · Bj?rn Smedman
Quoted 5 lines

Hi all,

The following patch attempts to fix some problems with ath9k tx queue selection:

Quoted 7 lines
Quoted 4 lines

1. There was a posible mismatch between the queue selected for QoS packets (on which locking, queue start/stop and statistics where performed) and the queue actually used for TX. This is fixed by selecting the tx queue based on the TID of the 802.11 header for this type of packet.

This should not be necessary. mac80211 should take care of queue selection properly for QoS frames. If it doesn't, then that is the bug that needs to be fixed...

The problem is rather that ath9k sets up its own skb -> txq mapping by tying the txq to the tid (tid -> ac -> txq). To understand better ask the question, should mac80211 be allowed to set the queue mapping to 1 but the qos data tid to 5? If the answer is yes then ath9k is broken. Even if the answer is no I don't really like that ath9k will corrupt DMA if somebody changes the queue mapping / tid logic in mac80211...

I agree however that there are better solutions (that's why the subject says RFC). If you want to honor the mapping set up by mac80211 then it might be better to break the connection tid ---> ac -X-> txq in xmit.c so that ampdu frames are always tx:ed on the queue in txctl->txq. However, that is not trivial to do since the aggregation logic depends on scheduling new aggregates from ath_tx_processq().

Quoted 7 lines
Quoted 5 lines

2. Even with the above fix there was still a risk of mac80211 queue "deadlock" because the queue to stop was selected on the basis of the skb queue mapping whereas the queue to start was selected based on the hardware tx queue to mac80211 queue mapping. These may not in all situations be one and the same.

Instead of working around this, we need to make sure that those are always identical.

But they cannot be... If we have for example hardware with only one tx queue then it is impossible to use the hw queue to mac80211 queue mapping. I see some comments here and there about such chipsets. In general I think we should assume mac80211 can have more queues than hardware, no?

Quoted 9 lines
Quoted 7 lines

This patch is against latest wireless-testing but I've only tested it against compat-wireless-2010-10-19 with openwrt patches on top (including Luis latest pcu lock patch) and some other patches I'm working on. If you can run wireless-testing directly, please give it a spin. For me it's a big improvement in stability under high tx/rx load.

Any thoughts?

Let's do a thorough review of the tx path and figure out where the mismatch is actually coming from.

It's quite complex but if you read through mac80211 and ath9k you will see the fundamental problem is that you cannot be sure that

#define TID_TO_WME_AC(_tid)                             \
        ((((_tid) == 0) || ((_tid) == 3)) ? WME_AC_BE : \
         (((_tid) == 1) || ((_tid) == 2)) ? WME_AC_BK : \
         (((_tid) == 4) || ((_tid) == 5)) ? WME_AC_VI : \
         WME_AC_VO)

will give you the same tid -> txq mapping as (some function of) skb_get_queue_mapping(). Or maybe you can, but then you should at least do something better than break DMA locking when that assumption yet again becomes false.

Quoted 1 line

- Felix

/Bj?rn

#15 lore raw
In reply to Felix Fietkau

Am Dienstag 02 November 2010 schrieb Felix Fietkau:

Quoted 11 lines · Björn Smedman
Quoted 7 lines

The following patch attempts to fix some problems with ath9k tx queue selection:

1. There was a posible mismatch between the queue selected for QoS packets (on which locking, queue start/stop and statistics where performed) and the queue actually used for TX. This is fixed by selecting the tx queue based on the TID of the 802.11 header for this type of packet.

This should not be necessary. mac80211 should take care of queue selection properly for QoS frames. If it doesn't, then that is the bug that needs to be fixed...

Not sure if this is related but I had some issues with rt2800pci and tx queue selection as well. This was caused by a bug in the net stack. See [1] for the details.

I don't have any clue if this also affects ath9k but this issue sounds similar.

Helmut

[1] http://www.spinics.net/lists/netdev/msg139832.html