Home
last modified time | relevance | path

Searched refs:collide (Results 1 – 10 of 10) sorted by relevance

/Linux-v4.19/net/ceph/crush/
Dmapper.c475 int collide, reject; in crush_choose_firstn() local
495 collide = 0; in crush_choose_firstn()
548 collide = 1; in crush_choose_firstn()
554 if (!collide && recurse_to_leaf) { in crush_choose_firstn()
585 if (!reject && !collide) { in crush_choose_firstn()
594 if (reject || collide) { in crush_choose_firstn()
598 if (collide && flocal <= local_retries) in crush_choose_firstn()
613 reject, collide, ftotal, in crush_choose_firstn()
664 int collide; in crush_choose_indep() local
763 collide = 0; in crush_choose_indep()
[all …]
/Linux-v4.19/tools/testing/selftests/futex/
DREADME55 problem as we intend to write multiple tests which collide in this namespace.
/Linux-v4.19/Documentation/arm/
Dmemory.txt81 Please note that mappings which collide with the above areas may result
/Linux-v4.19/Documentation/filesystems/ext4/ondisk/
Dattributes.rst142 xattr\_header/xattr\_entry table. When the two collide, the overflow is
/Linux-v4.19/Documentation/
Diostats.txt122 introduced when changes collide, so (for instance) adding up all the
/Linux-v4.19/Documentation/usb/
Dusb-serial.txt159 device ID isn't right, might collide with other Keyspan products
/Linux-v4.19/Documentation/s390/
DDebugging390.txt945 very seldom collide with text segments of user programs ( thanks Martin ),
947 However it is quite common for user processes to have addresses which collide
/Linux-v4.19/Documentation/process/
Dcoding-style.rst779 to collide with an existing variable.
/Linux-v4.19/Documentation/driver-api/
Dpinctl.rst737 0 and 1, uses one pin in common so they would collide.
/Linux-v4.19/Documentation/admin-guide/
Dcgroup-v2.rst542 directory and it is possible to create children cgroups which collide