1.. _net_offload_interface:
2
3Network Traffic Offloading
4==========================
5
6.. contents::
7    :local:
8    :depth: 2
9
10Network Offloading
11##################
12
13Overview
14********
15
16The network offloading API provides hooks that a device vendor can use
17to provide an alternate implementation for an IP stack. This means that the
18actual network connection creation, data transfer, etc., is done in the vendor
19HAL instead of the Zephyr network stack.
20
21API Reference
22*************
23
24.. doxygengroup:: net_offload
25
26.. _net_socket_offloading:
27
28Socket Offloading
29#################
30
31Overview
32********
33
34In addition to the network offloading API, Zephyr allows offloading of networking
35functionality at the socket API level. With this approach, vendors who provide an
36alternate implementation of the networking stack, exposing socket API for their
37networking devices, can easily integrate it with Zephyr.
38
39See :zephyr_file:`drivers/wifi/simplelink/simplelink_sockets.c` for a sample
40implementation on how to integrate network offloading at socket level.
41