From: "Filip Bakreski" <phial@phiality.com>
To: "Lorenzo Bianconi" <lorenzo@kernel.org>
Cc: nbd@nbd.name, ryder.lee@mediatek.com, shayne.chen@mediatek.com,
sean.wang@mediatek.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wifi: mt76: mt76u: use GRO on the USB RX path
Date: Tue, 09 Jun 2026 00:35:02 +0000 [thread overview]
Message-ID: <ba8109de16240cfcc150b90ff6b5a20fbb629671@phiality.com> (raw)
In-Reply-To: <aib-n_sCzWOjXFE1@lore-desk>
> I guess we do not need to add them, we can just reuse napi_dev pointer and
> napi[] array available in mt76_dev struct. Agree?
Agreed, I'll drop the new mt76_usb fields and reuse dev->napi_dev and dev->napi[MT_RXQ_MAIN] in v2
> I guess it would be interesting verifying if threaded-napi provides better
> results.
It does, on mt7921u a threaded NAPI servicing the RX queue averaged ~588 Mbit/s vs ~424 Mbit/s for the manually-driven NAPI. Suspend/resume also tested clean.
v2: https://lore.kernel.org/linux-wireless/20260609003224.132191-1-phial@phiality.com/
Thanks for the review,
Filip
prev parent reply other threads:[~2026-06-09 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 4:41 [PATCH] wifi: mt76: mt76u: use GRO on the USB RX path Filip Bakreski
2026-06-08 17:40 ` Lorenzo Bianconi
2026-06-09 0:35 ` Filip Bakreski [this message]
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=ba8109de16240cfcc150b90ff6b5a20fbb629671@phiality.com \
--to=phial@phiality.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
/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