| /linux/lib/ |
| H A D | lru_cache.c | 246 hlist_for_each_entry(e, lc_hash_slot(lc, enr), collision) { in __lc_find()
306 hlist_del_init(&e->collision); in lc_del()
327 if (!hlist_unhashed(&e->collision)) in lc_prepare_for_change()
328 __hlist_del(&e->collision); in lc_prepare_for_change()
329 hlist_add_head(&e->collision, lc_hash_slot(lc, new_number)); in lc_prepare_for_change()
|
| /linux/arch/arm64/boot/dts/xilinx/ |
| H A D | zynqmp-zcu102-revB.dts | 36 /* Fix collision with u61 */
|
| /linux/include/linux/ |
| H A D | lru_cache.h | 148 struct hlist_node collision; member
|
| /linux/Documentation/networking/device_drivers/ethernet/3com/ |
| H A D | 3c509.rst | 211 0x02 Out-of-window collision.
230 Out of window collision. This typically occurs when some other Ethernet
237 or when another host doesn't correctly back off after a collision. If this
|
| H A D | vortex.rst | 235 to increase this value on LANs which have very high collision rates.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-net-statistics | 132 a medium collision). See the network driver for the exact
215 due to a window collision. The specific meaning depends on the
|
| /linux/fs/smb/client/ |
| H A D | smb1ops.c | 216 bool collision, reconnect = false; in cifs_get_next_mid() local
241 collision = false; in cifs_get_next_mid()
252 collision = true; in cifs_get_next_mid()
271 if (!collision) { in cifs_get_next_mid()
|
| /linux/fs/netfs/ |
| H A D | fscache_cookie.c | 415 goto collision; in fscache_hash_cookie()
434 collision: in fscache_hash_cookie()
|
| /linux/Documentation/locking/ |
| H A D | futex-requeue-pi.rst | 107 result of a high-speed collision between futex_wait() and
|
| /linux/Documentation/usb/ |
| H A D | gadget_multi.rst | 103 so there will be no collision with other customised gadgets or the
|
| /linux/drivers/net/ethernet/marvell/ |
| H A D | mv643xx_eth.c | 318 u32 collision; member
1326 p->collision += mib_read(mp, 0x78); in mib_counters_update()
1477 MIBSTAT(collision),
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | directory.rst | 220 bit is set to 0. However, if there is a hash collision between directory
|
| /linux/kernel/ |
| H A D | workqueue.c | 1181 struct worker *collision; in assign_work() local
1193 collision = find_worker_executing_work(pool, work); in assign_work()
1194 if (unlikely(collision)) { in assign_work()
1195 move_linked_works(work, &collision->scheduled, nextp); in assign_work()
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | rsb.rst | 157 user forces a BTB collision then the RET can speculatively branch to a
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-arm-spe.txt | 89 When an operation is sampled while a previous sampled operation has not finished, a collision
|
| /linux/Documentation/virt/hyperv/ |
| H A D | vpci.rst | 90 collisions. The collision resolution is intended to be stable
|
| /linux/Documentation/process/ |
| H A D | submitting-patches.rst | 112 there is no collision with your six-character ID now, that condition may
|
| /linux/drivers/scsi/aic7xxx/ |
| H A D | aic79xx.seq | 62 * interrupt collision on the hardware
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 1493 part due to the collision of multicore hardware with object-oriented
|
| /linux/Documentation/admin-guide/ |
| H A D | cgroup-v2.rst | 645 character for collision avoidance. Also, interface file names won't
|
| /linux/Documentation/virt/kvm/ |
| H A D | api.rst | 4517 -ENOSPC if there was a hash collision when moving existing
|