:orphan:

.. title:: CONFIG_BT_MESH_ADV_BUF_COUNT

.. kconfig:: CONFIG_BT_MESH_ADV_BUF_COUNT

CONFIG_BT_MESH_ADV_BUF_COUNT
############################

*Number of advertising buffers*

Type: ``int``

Help
====

.. code-block:: none

    Number of advertising buffers available. This should be chosen
    based on what kind of features the local node should have. E.g.
    a relay will perform better the more buffers it has. Another
    thing to consider is outgoing segmented messages. There must
    be at least three more advertising buffers than the maximum
    supported outgoing segment count (BT_MESH_TX_SEG_MAX).

Direct dependencies
===================

\ :kconfig:`BT_MESH <CONFIG_BT_MESH>` && \ :kconfig:`BT <CONFIG_BT>`

*(Includes any dependencies from ifs and menus.)*

Default
=======

- 6

Kconfig definition
==================



At ``<Zephyr Subsystem>/bluetooth/mesh/Kconfig:255``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``<Zephyr Subsystem>/Kconfig:9`` → ``<Zephyr Subsystem>/bluetooth/Kconfig:193``

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

.. code-block:: kconfig

    config BT_MESH_ADV_BUF_COUNT
    	int "Number of advertising buffers"
    	range 1 256
    	default 6
    	depends on BT_MESH && BT
    	help
    	  Number of advertising buffers available. This should be chosen
    	  based on what kind of features the local node should have. E.g.
    	  a relay will perform better the more buffers it has. Another
    	  thing to consider is outgoing segmented messages. There must
    	  be at least three more advertising buffers than the maximum
    	  supported outgoing segment count (BT_MESH_TX_SEG_MAX).

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*