On Fri, Jun 19, 2020 at 09:24:07AM -0700, Ben Widawsky wrote: > This patch series introduces the concept of the MPOL_PREFERRED_MANY mempolicy. So the reason for having a new policy is that you're worried some legacy application passes multiple nodes to MPOL_PREFERRED, where all but the first would be currently ignored. Is that right? Is there any indication that this is actually the case? If not I would prefer to just extend the semantics of the existing MPOL_PREFERRED. Even if there was such an legacy application any legacy behavior changes are likely not fatal, because preferred is only a hint anyways. Anybody who really requires the right nodes would use _BIND. -Andi
