On Mon, 24 Aug 2009, Lee Schermerhorn wrote:
> [PATCH 1/5] hugetlb: rework hstate_next_node* functions
>
> Against: 2.6.31-rc6-mmotm-090820-1918
>
> V2:
> + cleaned up comments, removed some deemed unnecessary,
> add some suggested by review
> + removed check for !current in huge_mpol_nodes_allowed().
> + added 'current->comm' to warning message in huge_mpol_nodes_allowed().
> + added VM_BUG_ON() assertion in hugetlb.c next_node_allowed() to
> catch out of range node id.
> + add examples to patch description
>
> V3:
> + factored this "cleanup" patch out of V2 patch 2/3
> + moved ahead of patch to add nodes_allowed mask to alloc funcs
> as this patch is somewhat independent from using task mempolicy
> to control huge page allocation and freeing.
>
> Modify the hstate_next_node* functions to allow them to be called to
> obtain the "start_nid". Then, whereas prior to this patch we
> unconditionally called hstate_next_node_to_{alloc|free}(), whether
> or not we successfully allocated/freed a huge page on the node,
> now we only call these functions on failure to alloc/free to advance
> to next allowed node.
>
> Factor out the next_node_allowed() function to handle wrap at end
> of node_online_map. In this version, the allowed nodes include all
> of the online nodes.
>
> Reviewed-by: Mel Gorman <mel@xxxxxxxxx>
> Signed-off-by: Lee Schermerhorn <lee.schermerhorn@xxxxxx>
Acked-by: David Rientjes <rientjes@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-numa" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
