On Mon, 19 Apr 2010, Minchan Kim wrote: > Let's tidy my table. > > I made quick patch to show the concept with one example of pci-dma. > (Sorry but I attach patch since web gmail's mangling.) > > On UMA, we can change alloc_pages with > alloc_pages_exact_node(numa_node_id(),....) > (Actually, the patch is already merged mmotm) UMA does not have the concept of nodes. Whatever node you specify is irrelevant. Please remove the patch from mmotm. > on NUMA, alloc_pages is some different meaning, so I don't want to change it. No it has the same meaning. It means allocate a page. > on NUMA, alloc_pages_node means _ANY_NODE_. It means allocate on the indicated node if possible. Memory could come from any node due to fallback (in order of node preference). > So let's remove nid argument and change naming with alloc_pages_any_node. ??? What in the world are you doing? > Then, whole users of alloc_pages_node can be changed between > alloc_pages_exact_node and alloc_pages_any_node. > > It was my intention. What's your concern? I dont see the point. > again: > - page = alloc_pages_node(dev_to_node(dev), flag, get_order(size)); > + nid = dev_to_node(dev); > + /* > + * If pci-dma maintainer makes sure nid never has NUMA_NO_NODE > + * we can remove this ugly checking. > + */ > + if (nid == NUMA_NO_NODE) > + page = alloc_pages_any_node(flag, get_order(size)); s/alloc_pages_any_node/alloc_pages/ > + else > + page = alloc_pages_exact_node(nid, flag, get_order(size)); s/alloc_pages_exact_node/alloc_pages_node/ > -static inline struct page *alloc_pages_node(int nid, gfp_t gfp_mask, > +static inline struct page *alloc_pagse_any_node(gfp_t gfp_mask, > unsigned int order) > { > - /* Unknown node is current node */ > - if (nid < 0) > - nid = numa_node_id(); > - > + int nid = numa_node_id(); > return __alloc_pages(gfp_mask, order, node_zonelist(nid, gfp_mask)); > } > This is very confusing. Because it is alloc_pages_numa_node_id() alloca_pages_any_node suggests that the kernel randomly picks a node?