Lines Matching refs:case

35     Currently, the security library does not support the case of multi-process.
52 packet. e.g. In case of IPsec, the IPsec tunnel headers (if any),
123 packet. e.g. in the case of IPsec, the IPsec tunnel headers (if any),
134     The underlying device in this case is stateful. It is expected that
137     E.g. in case of IPsec the device may internally manage anti-replay etc.
155     processing. E.g. in case of IPsec, the seq number will be added to the
204 E.g. in case of IPsec, IPsec tunnel headers (if any), ESP/AH headers
210     In case of IPsec the device may internally manage anti-replay etc.
215 for encryption, the hardware device in this case will also add the relevant
222     In the case of IPsec, the seq number will be added to the packet,
297 Just like IPsec, in case of PDCP also header addition/deletion, cipher/
572     In case of inline processed packets, ``RTE_SECURITY_DYNFIELD_NAME`` field
668 In the case of NIC based offloads, the security session specified in the
677 flows can be specified to that SA. In the case of an ingress IPsec SA then