Bluetooth: ATT: Internalize ATT PDU TX pool
Why? - metadata is easier to manage as an array + index - less error-prone -> less memory-management bugs - we can. because of the previous refactor - PDU allocations are more predictable - ATT buffer size can be optimized by app - isolates ATT from the rest of the ACL users - decouples ATT PDU size from e.g. SMP w/ LESC Drawbacks: - higher memory usage - kconfig change The higher memory use is only temporary, as this will be followed-up with more refactors that should bring it back down. Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no> Co-authored-by: Aleksander Wasaznik <aleksander.wasaznik@nordicsemi.no>
This commit is contained in:
parent
47ec4359b9
commit
a05a47573a
10 changed files with 66 additions and 95 deletions
|
@ -8,7 +8,7 @@ CONFIG_UTF8=y
|
|||
|
||||
CONFIG_BT_SMP=y
|
||||
CONFIG_BT_KEYS_OVERWRITE_OLDEST=y
|
||||
CONFIG_BT_L2CAP_TX_BUF_COUNT=20
|
||||
CONFIG_BT_ATT_TX_COUNT=20
|
||||
|
||||
# TMAP support
|
||||
CONFIG_BT_TMAP=y
|
||||
|
|
|
@ -7,7 +7,7 @@ CONFIG_UTF8=y
|
|||
|
||||
CONFIG_BT_SMP=y
|
||||
CONFIG_BT_KEYS_OVERWRITE_OLDEST=y
|
||||
CONFIG_BT_L2CAP_TX_BUF_COUNT=20
|
||||
CONFIG_BT_ATT_TX_COUNT=20
|
||||
|
||||
# TMAP support
|
||||
CONFIG_BT_TMAP=y
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue