On Thu, 1 Nov 2012, Wen Congyang wrote: > > This doesn't describe why we need the new node state, unfortunately. It > > 1. Somethimes, we use the node which contains the memory that can be used by > kernel. > 2. Sometimes, we use the node which contains the memory. > > In case1, we use N_HIGH_MEMORY, and we use N_MEMORY in case2. > Yeah, that's clear, but the question is still _why_ we want two different nodemasks. I know that this part of the patchset simply introduces the new nodemask because the name "N_MEMORY" is more clear than "N_HIGH_MEMORY", but there's no real incentive for making that change by introducing a new nodemask where a simple rename would suffice. I can only assume that you want to later use one of them for a different purpose: those that do not include nodes that consist of only ZONE_MOVABLE. But that change for MPOL_BIND is nacked since it significantly changes the semantics of set_mempolicy() and you can't break userspace (see my response to that from yesterday). Until that problem is addressed, then there's no reason for the additional nodemask so nack on this series as well. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
