Searched refs:collision (Results 1 – 20 of 20) sorted by relevance
| /Linux-v5.4/arch/arm64/boot/dts/xilinx/ |
| D | zynqmp-zcu102-revB.dts | 30 /* Fix collision with u61 */
|
| /Linux-v5.4/Documentation/networking/device_drivers/3com/ |
| D | 3c509.txt | 181 0x02 Out-of-window collision.
197 Out of window collision. This typically occurs when some other Ethernet
202 or when another host doesn't correctly back off after a collision. If this
|
| D | vortex.txt | 224 to increase this value on LANs which have very high collision rates.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-net-statistics | 116 a medium collision). See the network driver for the exact
199 due to a window collision. The specific meaning depends on the
|
| /Linux-v5.4/fs/cifs/ |
| D | smb1ops.c | 165 bool collision; in cifs_get_next_mid() local
191 collision = false; in cifs_get_next_mid()
201 collision = true; in cifs_get_next_mid()
219 if (!collision) { in cifs_get_next_mid()
|
| /Linux-v5.4/fs/fscache/ |
| D | cookie.c | 208 goto collision; in fscache_hash_cookie()
218 collision: in fscache_hash_cookie()
|
| /Linux-v5.4/Documentation/filesystems/nfs/ |
| D | nfs.txt | 38 nfs.nfs4_unique_id stays the same, preventing collision with other clients
|
| /Linux-v5.4/Documentation/ |
| D | futex-requeue-pi.txt | 107 result of a high-speed collision between futex_wait() and
|
| /Linux-v5.4/drivers/perf/ |
| D | xgene_pmu.c | 353 XGENE_PMU_EVENT_ATTR(in-rd-collision, 0x0e),
354 XGENE_PMU_EVENT_ATTR(in-wr-collision, 0x0f),
355 XGENE_PMU_EVENT_ATTR(collision-queue-not-empty, 0x10),
356 XGENE_PMU_EVENT_ATTR(collision-queue-full, 0x11),
|
| /Linux-v5.4/Documentation/usb/ |
| D | gadget_multi.rst | 103 so there will be no collision with other customised gadgets or the
|
| /Linux-v5.4/Documentation/driver-api/i3c/ |
| D | protocol.rst | 75 Provisional ID collision, otherwise the discovery mechanism may fail.
|
| /Linux-v5.4/kernel/ |
| D | workqueue.c | 2170 struct worker *collision; in process_one_work() local
2193 collision = find_worker_executing_work(pool, work); in process_one_work()
2194 if (unlikely(collision)) { in process_one_work()
2195 move_linked_works(work, &collision->scheduled, NULL); in process_one_work()
|
| /Linux-v5.4/crypto/ |
| D | Kconfig | 891 security against collision attacks.
894 of security against collision attacks.
930 security against collision attacks.
933 of security against collision attacks.
|
| /Linux-v5.4/Documentation/filesystems/caching/ |
| D | object.txt | 318 state machine, it doesn't matter if there's a collision with both ends trying
|
| /Linux-v5.4/drivers/net/ethernet/marvell/ |
| D | mv643xx_eth.c | 317 u32 collision; member
1329 p->collision += mib_read(mp, 0x78); in mib_counters_update()
1479 MIBSTAT(collision),
|
| /Linux-v5.4/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 813 ``git commit`` command (it's capital ``-S`` due to collision with
|
| D | submitting-patches.rst | 180 there is no collision with your six-character ID now, that condition may
|
| /Linux-v5.4/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 62 * interrupt collision on the hardware
|
| /Linux-v5.4/Documentation/virt/kvm/ |
| D | api.txt | 3458 -ENOSPC if there was a hash collision when moving existing
3511 -ENOSPC if there was a hash collision when moving existing
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 560 character for collision avoidance. Also, interface file names won't
|
