Searched refs:collision (Results 1 – 20 of 20) sorted by relevance
| /Linux-v6.1/arch/arm64/boot/dts/xilinx/ |
| D | zynqmp-zcu102-revB.dts | 31 /* Fix collision with u61 */
|
| /Linux-v6.1/fs/fscache/ |
| D | volume.c | 173 goto collision; in fscache_hash_volume()
189 collision: in fscache_hash_volume()
|
| D | cookie.c | 415 goto collision; in fscache_hash_cookie()
434 collision: in fscache_hash_cookie()
|
| /Linux-v6.1/Documentation/networking/device_drivers/ethernet/3com/ |
| 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
|
| D | vortex.rst | 235 to increase this value on LANs which have very high collision rates.
|
| /Linux-v6.1/fs/cifs/ |
| D | smb1ops.c | 167 bool collision, reconnect = false; in cifs_get_next_mid() local
193 collision = false; in cifs_get_next_mid()
203 collision = true; in cifs_get_next_mid()
221 if (!collision) { in cifs_get_next_mid()
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| 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-v6.1/Documentation/locking/ |
| D | futex-requeue-pi.rst | 107 result of a high-speed collision between futex_wait() and
|
| /Linux-v6.1/drivers/perf/ |
| D | xgene_pmu.c | 350 XGENE_PMU_EVENT_ATTR(in-rd-collision, 0x0e),
351 XGENE_PMU_EVENT_ATTR(in-wr-collision, 0x0f),
352 XGENE_PMU_EVENT_ATTR(collision-queue-not-empty, 0x10),
353 XGENE_PMU_EVENT_ATTR(collision-queue-full, 0x11),
|
| /Linux-v6.1/Documentation/usb/ |
| D | gadget_multi.rst | 103 so there will be no collision with other customised gadgets or the
|
| /Linux-v6.1/tools/perf/Documentation/ |
| D | perf-arm-spe.txt | 89 When an operation is sampled while a previous sampled operation has not finished, a collision
|
| /Linux-v6.1/Documentation/driver-api/i3c/ |
| D | protocol.rst | 75 Provisional ID collision, otherwise the discovery mechanism may fail.
|
| /Linux-v6.1/kernel/ |
| D | workqueue.c | 2189 struct worker *collision; in process_one_work() local
2212 collision = find_worker_executing_work(pool, work); in process_one_work()
2213 if (unlikely(collision)) { in process_one_work()
2214 move_linked_works(work, &collision->scheduled, NULL); in process_one_work()
|
| /Linux-v6.1/drivers/net/ethernet/marvell/ |
| D | mv643xx_eth.c | 317 u32 collision; member
1325 p->collision += mib_read(mp, 0x78); in mib_counters_update()
1475 MIBSTAT(collision),
|
| /Linux-v6.1/Documentation/process/ |
| D | submitting-patches.rst | 112 there is no collision with your six-character ID now, that condition may
|
| D | maintainer-pgp-guide.rst | 802 ``git commit`` command (it's capital ``-S`` due to collision with
|
| /Linux-v6.1/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 62 * interrupt collision on the hardware
|
| /Linux-v6.1/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 1493 part due to the collision of multicore hardware with object-oriented
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 584 character for collision avoidance. Also, interface file names won't
|
| /Linux-v6.1/Documentation/virt/kvm/ |
| D | api.rst | 4379 -ENOSPC if there was a hash collision when moving existing
|
