Searched refs:collision (Results 1 – 16 of 16) sorted by relevance
66 security against collision attacks.69 of security against collision attacks.
39 u32 collision:1; member
95 if (unlikely(p->des01.rx.collision)) { in ndesc_get_rx_status()
181 0x02 Out-of-window collision.197 Out of window collision. This typically occurs when some other Ethernet202 or when another host doesn't correctly back off after a collision. If this
224 to increase this value on LANs which have very high collision rates.
174 bool collision; in cifs_get_next_mid() local197 collision = false; in cifs_get_next_mid()207 collision = true; in cifs_get_next_mid()225 if (!collision) { in cifs_get_next_mid()
116 a medium collision). See the network driver for the exact199 due to a window collision. The specific meaning depends on the
38 nfs.nfs4_unique_id stays the same, preventing collision with other clients
106 result of a high-speed collision between futex_wait() and
184 there is no collision with your six-character ID now, that condition may
92 so there will be no collision with other customised gadgets or the
612 security against collision attacks.615 of security against collision attacks.651 security against collision attacks.654 of security against collision attacks.
2005 struct worker *collision; in process_one_work() local2028 collision = find_worker_executing_work(pool, work); in process_one_work()2029 if (unlikely(collision)) { in process_one_work()2030 move_linked_works(work, &collision->scheduled, NULL); in process_one_work()
331 u32 collision; member1313 p->collision += mib_read(mp, 0x78); in mib_counters_update()1461 MIBSTAT(collision),
318 state machine, it doesn't matter if there's a collision with both ends trying
62 * interrupt collision on the hardware