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.

Direct dependencies¶

BT_MESH && BT

(Includes any dependencies from ifs and menus.)

Default¶

64

Kconfig definition¶

At <Zephyr>/subsys/bluetooth/mesh/Kconfig:281

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:8 → <Zephyr>/subsys/bluetooth/Kconfig:258

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Bluetooth Mesh support

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.)