:orphan: .. title:: CONFIG_NET_HEADERS_ALWAYS_CONTIGUOUS .. kconfig:: CONFIG_NET_HEADERS_ALWAYS_CONTIGUOUS CONFIG_NET_HEADERS_ALWAYS_CONTIGUOUS #################################### *(No prompt -- not directly user assignable.)* Type: ``bool`` Help ==== .. code-block:: none This a hidden option, which one should use with a lot of care. NO bug reports will be accepted if that option is enabled! You are warned. If you are 100% sure the headers memory space is always in a contiguous space, this will save stack usage and ROM in net core. This is a possible case when using IPv4 only, with NET_BUF_FIXED_DATA_SIZE enabled and NET_BUF_DATA_SIZE of 128 for instance. Direct dependencies =================== \ :kconfig:`NETWORKING ` *(Includes any dependencies from ifs and menus.)* Defaults ======== No defaults. Implicitly defaults to ``n``. Kconfig definition ================== At ``/net/ip/Kconfig:688`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``/Kconfig:39`` → ``/net/Kconfig:87`` Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → IP stack .. code-block:: kconfig config NET_HEADERS_ALWAYS_CONTIGUOUS bool depends on NETWORKING help This a hidden option, which one should use with a lot of care. NO bug reports will be accepted if that option is enabled! You are warned. If you are 100% sure the headers memory space is always in a contiguous space, this will save stack usage and ROM in net core. This is a possible case when using IPv4 only, with NET_BUF_FIXED_DATA_SIZE enabled and NET_BUF_DATA_SIZE of 128 for instance. *(The 'depends on' condition includes propagated dependencies from ifs and menus.)*