:orphan:

.. title:: CONFIG_NET_SOCKETS_OFFLOAD

.. kconfig:: CONFIG_NET_SOCKETS_OFFLOAD

CONFIG_NET_SOCKETS_OFFLOAD
##########################

*Offload Socket APIs [EXPERIMENTAL]*

Type: ``bool``

Help
====

.. code-block:: none

    Enables direct offloading of socket operations to dedicated TCP/IP
    hardware.
    This feature is intended to save resources by bypassing the Zephyr
    TCP/IP stack in the case where there is only one network interface
    required in the system, providing full BSD socket offload capability.
    As a result, it bypasses any potential IP routing that Zephyr might
    provide between multiple network interfaces.
    See NET_OFFLOAD for a more deeply integrated approach which offloads
    from the net_context() API within the Zephyr IP stack.

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

\ :kconfig:`NET_SOCKETS <CONFIG_NET_SOCKETS>` && \ :kconfig:`NETWORKING <CONFIG_NETWORKING>`

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

Defaults
========

No defaults. Implicitly defaults to ``n``.

Symbols that select this symbol
===============================

- \ :kconfig:`MODEM_UBLOX_SARA <CONFIG_MODEM_UBLOX_SARA>`
- \ :kconfig:`MODEM_QUECTEL_BG9X <CONFIG_MODEM_QUECTEL_BG9X>`

Symbols that imply this symbol
==============================

- \ :kconfig:`WIFI_ESWIFI <CONFIG_WIFI_ESWIFI>`

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



At ``<Zephyr Subsystem>/net/lib/sockets/Kconfig:136``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``<Zephyr Subsystem>/Kconfig:39`` → ``<Zephyr Subsystem>/net/Kconfig:89`` → ``<Zephyr Subsystem>/net/lib/Kconfig:30``

Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → Network Libraries → BSD Sockets compatible API

.. code-block:: kconfig

    config NET_SOCKETS_OFFLOAD
    	bool "Offload Socket APIs [EXPERIMENTAL]"
    	depends on NET_SOCKETS && NETWORKING
    	help
    	  Enables direct offloading of socket operations to dedicated TCP/IP
    	  hardware.
    	  This feature is intended to save resources by bypassing the Zephyr
    	  TCP/IP stack in the case where there is only one network interface
    	  required in the system, providing full BSD socket offload capability.
    	  As a result, it bypasses any potential IP routing that Zephyr might
    	  provide between multiple network interfaces.
    	  See NET_OFFLOAD for a more deeply integrated approach which offloads
    	  from the net_context() API within the Zephyr IP stack.

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