MT7981: MT7915_TX_RING_SIZE > 300 affects performance
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
Two devices with MT7981 with the same drivers 05-17-2024,
without WED,
160Mhz AX,
AP <-> STA,
iperf3 on devices. single stream
MT7915_TX_RING_SIZE = 2048
STA ---> AP
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-30.00 sec 2.88 GBytes 826 Mbits/sec 0 sender
[ 5] 0.00-30.01 sec 2.88 GBytes 825 Mbits/sec receiver
AP ----> STA
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-30.01 sec 3.99 GBytes 1.14 Gbits/sec 0 sender
[ 5] 0.00-30.00 sec 3.99 GBytes 1.14 Gbits/sec receiver
MT7915_TX_RING_SIZE = 256
STA ---> AP
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-30.01 sec 3.99 GBytes 1.14 Gbits/sec 0 sender
[ 5] 0.00-30.00 sec 3.99 GBytes 1.14 Gbits/sec receiver
AP ----> STA
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-30.01 sec 4.51 GBytes 1.29 Gbits/sec 0 sender
[ 5] 0.00-30.00 sec 4.51 GBytes 1.29 Gbits/sec receiver
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the MT7915_TX_RING_SIZE definition and the MT7981 driver path. Reproduce the reported STA-to-AP and AP-to-STA iperf3 tests with ring sizes 2048 and 256, then inspect the driver behavior affecting throughput. Done means identifying the cause and documenting or correcting the performance regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100