Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support config option to unify TX and RX net pkts and bufs #83257

Open
MaochenWang1 opened this issue Dec 20, 2024 · 1 comment
Open

Support config option to unify TX and RX net pkts and bufs #83257

MaochenWang1 opened this issue Dec 20, 2024 · 1 comment
Assignees
Labels
area: Networking Enhancement Changes/Updates/Additions to existing features

Comments

@MaochenWang1
Copy link
Collaborator

Is your enhancement proposal related to a problem? Please describe.
Currently net pkts and net bufs are divided into TX and RX, which will consume more footprint for memory constraint device.
Usually for Wi-Fi device, there are net buffers must be used for RX-reorder, but these buffers can't be used for TX.

Describe the solution you'd like
Default still use separate buf for TX and RX.
Support config option to use one kind of pkt/buf for both TX and RX.

@MaochenWang1 MaochenWang1 added Enhancement Changes/Updates/Additions to existing features area: Networking net-review To be discussed in the Networking Forum labels Dec 20, 2024
@MaochenWang1 MaochenWang1 removed the net-review To be discussed in the Networking Forum label Dec 20, 2024
@jukkar
Copy link
Member

jukkar commented Dec 20, 2024

We had at some point in the past, a shared net_buf pools for TX and RX, but then divided the usage because of the problems. One big issue with one net_buf pool is that if there is high amount of incoming packets it would prevent packet sending. It is very difficult to control the incoming data rate in that case without distrupting the ongoing network connections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Networking Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Development

No branches or pull requests

3 participants