[API-NEXT,v2,1/15] api: don't create special case for the tunnel-dummy packets

Message ID 1519236011-14987-2-git-send-email-odpbot@yandex.ru
State New
Headers show
  • [API-NEXT,v2,1/15] api: don't create special case for the tunnel-dummy packets
Related show

Commit Message

Github ODP bot Feb. 21, 2018, 5:59 p.m.
From: Dmitry Eremin-Solenikov <dmitry.ereminsolenikov@linaro.org>

Do not create special case for IPsec packet contents. It is easier to
always use odp_packet_len() - odp_packet_l3_offset() + tfc_pad_len as
the transformation length, rather than hardcoding special case.

Signed-off-by: Dmitry Eremin-Solenikov <dmitry.ereminsolenikov@linaro.org>

/** Email created from pull request 494 (lumag:ipsec-tfc-imp)
 ** https://github.com/Linaro/odp/pull/494
 ** Patch: https://github.com/Linaro/odp/pull/494.patch
 ** Base sha: ea2afab619ae74108a03798bc358fdfcd29fdd88
 ** Merge commit sha: 0b6ae2680a00027c3958ebcafbbcf92642a68f5e
 include/odp/api/spec/ipsec.h | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)


diff --git a/include/odp/api/spec/ipsec.h b/include/odp/api/spec/ipsec.h
index 2d1c4d9ba..474055c0c 100644
--- a/include/odp/api/spec/ipsec.h
+++ b/include/odp/api/spec/ipsec.h
@@ -1346,9 +1346,7 @@  int odp_ipsec_in(const odp_packet_t pkt_in[], int num_in,
  * and content of packet data before the IP header is undefined. Use outbound
  * operation parameters to specify the amount of TFC padding appended to
  * the packet during IPSEC transformation. Options can be used also to create
- * TFC dummy packets. Packet data content is ignored in tunnel mode TFC dummy
- * packet creation as tfc_pad_len option defines solely the packet length.
- * In all other cases, payload length for the IPSEC transformation is specified
+ * TFC dummy packets. Payload length for the IPSEC transformation is specified
  * by odp_packet_len() minus odp_packet_l3_offset() plus tfc_pad_len option.
  * Each successfully transformed packet has a valid value for these metadata: