Searched refs:fragment (Results 1 – 9 of 9) sorted by relevance
16 For each fragment two new mbufs are created:18 * Direct mbuf -- mbuf that will contain L3 header of the new fragment.21 It's data field points to the start of the original packets data plus fragment offset.26 … and 'indirect' mbufs for each fragment are linked together via mbuf's next filed to compose a pac…89 #. Update the entry with new fragment information and check if a packet can be reassembled97 (e.g: can't insert new entry into the Fragment Table, or invalid/timed-out fragment),
1263 Matches the presence of IPv6 fragment extension header.1265 - ``hdr``: IPv6 fragment extension header definition (``rte_ip.h``).
103 fragment extension header are present in the packet.157 :start-after: mbufs stored in the fragment table. 8<165 If the packet is an IPv4 or IPv6 fragment, then it calls rte_ipv4_reassemble_packet() for IPv4 pack…187 #. Update the entry with new fragment information and check195 (can't insert new entry into the Fragment table, or invalid/timed-out fragment),
236 * ``--reassemble NUM``: max number of entries in reassemble fragment table.245 * ``--frag-ttl FRAG_TTL_NS``: fragment lifetime (in nanoseconds).
90 bool fragment; member
483 if (flags->fragment) { in test_ipsec_td_prepare()786 flags->fragment) { in test_ipsec_td_verify()
9477 flags.fragment = true; in test_ipsec_proto_known_vec_fragmented()9859 flags.fragment = true; in test_ipsec_proto_pkt_fragment()
153 but constitutes only a small fragment of a file,
1359 after UDP GSO, only the first output fragment has the original UDP