Searched refs:lookups (Results 1 – 6 of 6) sorted by relevance
345 for hash-based lookups is done by the get_ipv4_dst_port() or get_ipv6_dst_port() function.350 :start-after: Performing hash-based lookups. 8<351 :end-before: >8 End of performing hash-based lookups.397 for LPM-based lookups is done by the get_ipv4_dst_port() function below:401 :start-after: Performing LPM-based lookups. 8<402 :end-before: >8 End of performing LPM-based lookups.408 it does not have separate functions for single and bulk lookups.409 ``rte_fib_lookup_bulk`` is used for IPv4 lookups
101 IPsec. There are no lookups, no routing done in the application. And for inline109 application (non librte_ipsec path). All the lookups, routing follows existing
221 not store the keys and is used for lookups) will be allocated and368 The design principle of EFD is that lookups are much more frequent than369 inserts, and hence, EFD's design optimizes for the lookups which are390 When discussing EFD inserts and lookups, the discussion is simplified by
28 lookups of values can be performed in parallel in multiple threads.
81 …ppropriately setting the flag. In all modes of operation lookups are thread-safe meaning lookups c…
1095 There is usually a performance limit on the number of table lookups