Lines Matching refs:offload

18 Luckily, there are NICs that offer a hardware based IPsec offload which
21 hardware offload.
23 Right now, there are two types of hardware offload that kernel supports.
24  * IPsec crypto offload:
27  * IPsec packet offload:
34 Userland access to the offload is typically through a system such as
37 like this for crypto offload:
43      offload dev eth4 dir in
45 and for packet offload
51      offload packet dev eth4 dir in
53   ip x p add src 14.0.0.70 dst 14.0.0.52 offload packet dev eth4 dir in
67         /* Crypto and Packet offload callbacks */
75         /* Solely packet offload callbacks */
82 The NIC driver offering ipsec offload will need to implement callbacks
83 relevant to supported offload to make the offload available to the network
85 NETIF_F_HW_ESP_TX_CSUM will signal the availability of the offload.
102 When new SAs are set up with a request for "offload" feature, the
108 	- enable the HW offload of the SA
113 		-EOPNETSUPP   offload not supported, try SW IPsec,
114                               not applicable for packet offload mode
119 that can be used to convey context into the fast-path offload requests::
125 been setup for offload, it first calls into xdo_dev_offload_ok() with
126 the skb and the intended offload state to ask the driver if the offload
128 offload can be supported (e.g. IPv4 or IPv6, no IPv4 options, etc) and
131 Crypto offload mode:
133 offload information, including the opaque context, and set up the packet
141 packet data, the offload just needs to do the encryption and fix up the
164 	indicate the success and/or error status of the offload::
175 Packet offload mode:
181 and xdo_dev_policy_delete() are asked to disable the offload.  Later,
185 offload state.  How these are used by the driver will depend on specific