Searched refs:collision (Results 1 – 10 of 10) sorted by relevance
103 ensure a collision.114 hash value to produce a collision for.134 collision generation task requires only the ``log2(RETA_SZ)`` bits in the147 could be altered to produce a hash collision. On success it writes a specially255 collision. This is shown in the code below.
59 When the collision occurs and all 2 \* <bucket_entries> are occupied,
100 because of hash collision) stored in this index and corresponding values
3480 - ``EEXIST``: collision with an existing rule. Only returned if device3481 supports flow rule collision checking and there was a flow rule3482 collision. Not receiving this return code is no guarantee that creating3483 the rule will not fail due to a collision.
476 uint32_t collision; /**< Number of filters with collision. */ member
1348 info->collision = (uint16_t)((reg & IXGBE_FDIRFREE_COLL_MASK) >> in ixgbe_fdir_stats_get()1372 fdir_stats->collision = info->collision; in ixgbe_fdir_stats_get()
201 uint16_t collision; member
121 uint16_t collision; member
435 collision: 0 free: 0
5809 fdir_stat.collision, fdir_stat.free, in fdir_get_infos()