You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: