Searched refs:collide (Results 1 – 8 of 8) sorted by relevance
426 int collide, reject; in crush_choose_firstn() local446 collide = 0; in crush_choose_firstn()492 collide = 1; in crush_choose_firstn()498 if (!collide && recurse_to_leaf) { in crush_choose_firstn()536 if (reject || collide) { in crush_choose_firstn()540 if (collide && flocal <= local_retries) in crush_choose_firstn()555 reject, collide, ftotal, in crush_choose_firstn()600 int collide; in crush_choose_indep() local680 collide = 0; in crush_choose_indep()683 collide = 1; in crush_choose_indep()[all …]
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.
727 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