Searched refs:signatures (Results 1 – 5 of 5) sorted by relevance
139 temp_signature = signatures[i]; in shuffle_input_keys()143 signatures[i] = signatures[swap_idx]; in shuffle_input_keys()227 signatures[i]); in get_input_keys()269 signatures[i], data); in timed_adds()277 signatures[i]); in timed_adds()334 signatures[j], &ret_data); in timed_lookups()349 signatures[j]); in timed_lookups()444 &signatures[j * BURST_SIZE], in timed_lookups_multi()460 (void *)((uintptr_t)signatures[ in timed_lookups_multi()476 &signatures[j * BURST_SIZE], in timed_lookups_multi()[all …]
200 does not match any attack signatures in the database to establish its204 and the major difference is that HTSS stores only the signatures but not the210 to. Because signatures can collide, HTSS can still has false positive
19 flows to signatures in flow tables to send incoming packets to their106 signatures and target values. This doesn't allow this scheme to scale to
292 it is desirable to have the key signatures evenly distributed across these intervals (uniform distr…293 as opposed to most of the signatures going into only a few of the intervals638 …| | | Set bit 0 of the signature to 1 (to match only signatures of val…644 …| 2 | Prefetch table key | Read the key signatures from the bucket. …646 … | Compare the signature of the input key against the 4 key signatures from the |
143 …ture comparison is done first and the full key comparison is done only when the signatures matches.