Searched refs:collide (Results 1 – 9 of 9) sorted by relevance
433 int collide, reject; in crush_choose_firstn() local453 collide = 0; in crush_choose_firstn()499 collide = 1; in crush_choose_firstn()505 if (!collide && recurse_to_leaf) { in crush_choose_firstn()543 if (reject || collide) { in crush_choose_firstn()547 if (collide && flocal <= local_retries) in crush_choose_firstn()562 reject, collide, ftotal, in crush_choose_firstn()611 int collide; in crush_choose_indep() local705 collide = 0; in crush_choose_indep()708 collide = 1; in crush_choose_indep()[all …]
55 problem as we intend to write multiple tests which collide in this namespace.
81 Please note that mappings which collide with the above areas may result
96 introduced when changes collide, so (for instance) adding up all the
676 to collide with an existing variable.
728 0 and 1, uses one pin in common so they would collide.
159 device ID isn't right, might collide with other Keyspan products
945 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
351 specified. Ensure multiplex ids do not collide. Fix case in which