:orphan: .. title:: CONFIG_BT_MESH_SEG_BUFS .. kconfig:: CONFIG_BT_MESH_SEG_BUFS CONFIG_BT_MESH_SEG_BUFS ####################### *Number of segment buffers available* Type: ``int`` Help ==== .. code-block:: none The incoming and outgoing segmented messages allocate their segments from the same pool. Each segment is a 12 byte block, and may only be used by one message at the time. Outgoing messages will allocate their segments at the start of the transmission, and release them one by one as soon as they have been acknowledged by the receiver. Incoming messages allocate all their segments at the start of the transaction, and won't release them until the message is fully received. Direct dependencies =================== \ :kconfig:`BT_MESH ` && \ :kconfig:`BT ` *(Includes any dependencies from ifs and menus.)* Default ======= - 64 Kconfig definition ================== At ``/bluetooth/mesh/Kconfig:360`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``/Kconfig:9`` → ``/bluetooth/Kconfig:193`` Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Bluetooth mesh support .. code-block:: kconfig config BT_MESH_SEG_BUFS int "Number of segment buffers available" range BT_MESH_RX_SEG_MAX 16384 if BT_MESH_RX_SEG_MAX > BT_MESH_TX_SEG_MAX range BT_MESH_TX_SEG_MAX 16384 default 64 depends on BT_MESH && BT help The incoming and outgoing segmented messages allocate their segments from the same pool. Each segment is a 12 byte block, and may only be used by one message at the time. Outgoing messages will allocate their segments at the start of the transmission, and release them one by one as soon as they have been acknowledged by the receiver. Incoming messages allocate all their segments at the start of the transaction, and won't release them until the message is fully received. *(The 'depends on' condition includes propagated dependencies from ifs and menus.)*