:orphan:

.. title:: NET_SOCKETS_OFFLOAD

.. option:: CONFIG_NET_SOCKETS_OFFLOAD

*Offload Socket APIs [EXPERIMENTAL]*

Type: ``bool``

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.

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

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

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

Defaults
========

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

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

- \ :option:`WIFI_ESWIFI <CONFIG_WIFI_ESWIFI>`
- \ :option:`MODEM_UBLOX_SARA <CONFIG_MODEM_UBLOX_SARA>`
- \ :option:`MODEM_QUECTEL_BG9X <CONFIG_MODEM_QUECTEL_BG9X>`

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

.. highlight:: kconfig

At ``subsys/net/lib/sockets/Kconfig:128``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:37`` → ``subsys/net/Kconfig:89`` → ``subsys/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

.. parsed-literal::

    config NET_SOCKETS_OFFLOAD
    	bool "Offload Socket APIs [EXPERIMENTAL]"
    	depends on \ :option:`NET_SOCKETS <CONFIG_NET_SOCKETS>` && \ :option:`NETWORKING <CONFIG_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.)*