From: Ping-Ke Shih <pkshih@realtek.com>
To: Luka Gejak <luka.gejak@linux.dev>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Michael Straube" <straube.linux@gmail.com>,
Peter Robinson <pbrobinson@gmail.com>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH v11 4/7] wifi: rtw88: sdio: zero the padding added to a TX transfer
Date: Fri, 11 Sep 2026 00:53:49 +0000 [thread overview]
Message-ID: <a17a665d7d4c47fbb33e038d122ed200@realtek.com> (raw)
In-Reply-To: <2294d792e937441fbf4ef8169c03df18@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
> Luka Gejak <luka.gejak@linux.dev> wrote:
> > mac80211 reserves IEEE80211_ENCRYPT_TAILROOM, 18 bytes, and offers
> > no way for a driver to ask for more on TX; extra_tx_headroom is headroom
> > and extra_beacon_tailroom is beacons only.
>
> You can modify mac80211 to reserve larger ndev->needed_tailroom to
> see if it can really resolve the symptom. If so, you can propose
> to add fields for tailroom like headroom:
>
> struct ieee80211_hw:: extra_tx_tailroom
> struct ieee80211_local:: tx_headroom
>
Note that the ndev->needed_tailroom isn't guaranteed by comments, so doing
some experiments by normal use case would be helpful to know if it's worth.
* @needed_tailroom: Extra tailroom the hardware may need, but not in all
* cases can this be guaranteed. Some cases also use
* LL_MAX_HEADER instead to allocate the skb
Ping-Ke
next prev parent reply other threads:[~2026-09-11 0:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 7:45 [PATCH v11 0/7] wifi: rtw88: preparations for RTL8723B/RTL8723BS luka.gejak
2026-09-09 7:45 ` [PATCH v11 1/7] wifi: rtw88: add the RTL8723B chip type and SDIO helper luka.gejak
2026-09-09 7:45 ` [PATCH v11 2/7] wifi: rtw88: rx: mark zero length packets on RTL8723BS luka.gejak
2026-09-09 7:45 ` [PATCH v11 3/7] wifi: rtw88: tx: extend the TX report purge timeout to RTL8723BS luka.gejak
2026-09-09 7:45 ` [PATCH v11 4/7] wifi: rtw88: sdio: zero the padding added to a TX transfer luka.gejak
2026-09-10 2:24 ` Ping-Ke Shih
2026-09-10 14:56 ` Luka Gejak
2026-09-10 15:51 ` Luka Gejak
2026-09-11 0:45 ` Ping-Ke Shih
2026-09-11 0:53 ` Ping-Ke Shih [this message]
2026-09-11 7:40 ` Luka Gejak
2026-09-11 7:45 ` Ping-Ke Shih
2026-09-11 8:42 ` Luka Gejak
2026-09-11 0:30 ` Ping-Ke Shih
2026-09-11 6:41 ` Luka Gejak
2026-09-09 7:45 ` [PATCH v11 5/7] wifi: rtw88: sdio: track free TX pages and OQT credits for RTL8723BS luka.gejak
2026-09-10 2:40 ` Ping-Ke Shih
2026-09-09 7:45 ` [PATCH v11 6/7] wifi: rtw88: sdio: set up RX aggregation and interrupts " luka.gejak
2026-09-09 7:45 ` [PATCH v11 7/7] wifi: rtw88: sdio: add TX back-pressure and retry on page starvation luka.gejak
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=a17a665d7d4c47fbb33e038d122ed200@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=pbrobinson@gmail.com \
--cc=rtl8821cerfe2@gmail.com \
--cc=straube.linux@gmail.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
all inboxes | Powered by JetHome®