Home
last modified time | relevance | path

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

/openbmc/linux/net/ceph/crush/
H A 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 …]
/openbmc/qemu/tests/qapi-schema/
H A Dreserved-command-q.json2 # We reject names like 'q-unix', because they can collide with the mangled
H A Dreserved-enum-q.json2 # We reject names like 'q-unix', because they can collide with the mangled
H A Dreserved-member-q.json2 # We reject names like 'q-unix', because they can collide with the mangled
H A Dreserved-member-has.json2 # We reject names like 'has-a', because they can collide with the flag
/openbmc/linux/tools/testing/selftests/futex/
H A DREADME55 problem as we intend to write multiple tests which collide in this namespace.
/openbmc/linux/Documentation/arch/arm/
H A Dmemory.rst96 Please note that mappings which collide with the above areas may result
/openbmc/linux/Documentation/filesystems/ext4/
H A Dattributes.rst142 xattr_header/xattr_entry table. When the two collide, the overflow is
/openbmc/openbmc/meta-google/recipes-google/networking/
H A Dgbmc-bridge.bb68 # same offset in the same machine network, it will collide with others.
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/
H A D0017-Platform-CS1000-Remove-unused-BL1-files.patch57 -# configuration, where image number is 3. (Coming from BL2 build). To not to collide with BL1's
/openbmc/openbmc/poky/documentation/test-manual/
H A Druntime-testing.rst354 Be sure that module names do not collide with module names used in
453 - Do not use module names that collide with existing core tests.
/openbmc/linux/Documentation/admin-guide/
H A Diostats.rst136 introduced when changes collide, so (for instance) adding up all the
H A Dcgroup-v2.rst577 directory and it is possible to create children cgroups which collide
/openbmc/linux/Documentation/usb/
H A Dusb-serial.rst173 - device ID isn't right, might collide with other Keyspan products
/openbmc/qemu/tcg/loongarch64/
H A Dtcg-target.c.inc231 * not collide with potential future additions to the true ELF relocation
/openbmc/linux/Documentation/arch/x86/
H A Dboot.rst991 without \0 at the end of the string, which does not collide with
/openbmc/linux/Documentation/process/
H A Dcoding-style.rst875 to collide with an existing variable.
/openbmc/linux/Documentation/driver-api/
H A Dpin-control.rst682 0 and 2, uses pin 24 in common so they would collide. All the same for