From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Georgios Karantzas <gck.kara@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Georgios Karantzas <gck.kara@gmail.com>
Subject: Re: [PATCH] wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE
Date: Wed, 09 Sep 2026 13:49:50 +0200 [thread overview]
Message-ID: <875x0efxup.fsf@toke.dk> (raw)
In-Reply-To: <20260831173931.1672-1-gck.kara@gmail.com>
Georgios Karantzas <gck.kara@gmail.com> writes:
> __hif_usb_tx() dequeues up to MAX_TX_AGGR_NUM (20) frames into a single tx_buf of MAX_TX_BUF_SIZE (32768) bytes, limiting the batch by record count but never by cumulative byte length.
>
> With large frames (MTU 2304), 20 aggregated frames of 2292 bytes each exceed the allocation (20 * 2296 = 45920 bytes), so the memcpy() in the loop writes up to 13152 bytes past tx_buf->buf before usb_submit_urb().
>
> Peek the queue head and stop before copying any record that would cross MAX_TX_BUF_SIZE, then dispatch the current batch. Leftover skbs remain queued and are drained on the next URB completion.
>
> Signed-off-by: Georgios Karantzas <gck.kara@gmail.com>
Please wrap the commit message at 72 characters.
> ---
> drivers/net/wireless/ath/ath9k/hif_usb.c | 29 +++++++++++++-----------
> 1 file changed, 16 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/hif_usb.c b/drivers/net/wireless/ath/ath9k/hif_usb.c
> index 0a3d2190b..3e9d0c59b 100644
> --- a/drivers/net/wireless/ath/ath9k/hif_usb.c
> +++ b/drivers/net/wireless/ath/ath9k/hif_usb.c
> @@ -328,32 +328,35 @@ static int __hif_usb_tx(struct hif_device_usb *hif_dev)
> tx_skb_cnt = min_t(u16, hif_dev->tx.tx_skb_cnt, MAX_TX_AGGR_NUM);
>
> for (i = 0; i < tx_skb_cnt; i++) {
> - nskb = __skb_dequeue(&hif_dev->tx.tx_skb_queue);
> + nskb = skb_peek(&hif_dev->tx.tx_skb_queue);
> + if (!nskb)
> + break;
>
> - /* Should never be NULL */
> - BUG_ON(!nskb);
> + if (tx_buf->offset + nskb->len + 4 > MAX_TX_BUF_SIZE)
> + break;
>
> + nskb = __skb_dequeue(&hif_dev->tx.tx_skb_queue);
> hif_dev->tx.tx_skb_cnt--;
This bit is fine...
> - buf = tx_buf->buf;
> - buf += tx_buf->offset;
> + buf = tx_buf->buf + tx_buf->offset;
> hdr = (__le16 *)buf;
> *hdr++ = cpu_to_le16(nskb->len);
> *hdr++ = cpu_to_le16(ATH_USB_TX_STREAM_MODE_TAG);
> - buf += 4;
> - memcpy(buf, nskb->data, nskb->len);
> - tx_buf->len = nskb->len + 4;
> -
> - if (i < (tx_skb_cnt - 1))
> - tx_buf->offset += (((tx_buf->len - 1) / 4) + 1) * 4;
> + memcpy(buf + 4, nskb->data, nskb->len);
>
> - if (i == (tx_skb_cnt - 1))
> - tx_buf->len += tx_buf->offset;
> + tx_buf->len = tx_buf->offset + nskb->len + 4;
> + tx_buf->offset += (((tx_buf->len - 1) / 4) + 1) * 4;
But this bit seems unrelated (and wrong?); please drop.
> __skb_queue_tail(&tx_buf->skb_queue, nskb);
> TX_STAT_INC(hif_dev, skb_queued);
> }
>
> + if (!i) {
> + list_move_tail(&tx_buf->list, &hif_dev->tx.tx_buf);
> + hif_dev->tx.tx_buf_cnt++;
> + return 0;
> + }
It's not possible for a single packet to overflow the buffer size, so
we'll never hit this. So let's not add a pointless check.
-Toke
next prev parent reply other threads:[~2026-09-09 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 17:39 Georgios Karantzas
2026-09-09 11:49 ` Toke Høiland-Jørgensen [this message]
2026-09-09 18:59 ` [PATCH v2] " Georgios Karantzas
2026-09-10 18:25 ` Toke Høiland-Jørgensen
2026-09-11 0:11 ` [PATCH v3] " Georgios Karantzas
2026-09-11 10:20 ` Toke Høiland-Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875x0efxup.fsf@toke.dk \
--to=toke@toke.dk \
--cc=gck.kara@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®