Dear All, On Sat, Oct 30, 2010 at 2:00 AM, Lee Schermerhorn <Lee.Schermerhorn@xxxxxx> wrote: > > Also, if you could add "mminit_loglevel=2" to the boot command line, and > grep for 'zonelist general'. ÂThe general zonelists for the Normal zones > will show the order of allocation for the two nodes. ÂOn a 2 node [AMD] > platform, I see: > Output of "mminit_loglevel=2" ... mminit::zonelist general 0:DMA = 0:DMA mminit::zonelist general 0:DMA32 = 0:DMA32 0:DMA mminit::zonelist general 0:Normal = 0:Normal 1:Normal 0:DMA32 0:DMA mminit::zonelist general 1:Normal = 1:Normal 0:Normal 0:DMA32 0:DMA > > And, just to be sure, you could suspend your dd job [^Z] and take a look > at it's mempolicy and such via /proc/<pid>/status [Mems_allowed*] and > it's /proc/<pid>/numa_maps. Â If you haven't changed anything you should > see Âboth nodes in Mems_allowed[_list] and all of the policies in the > numa_maps should show 'default'. > /proc/<PID>/numa_maps shows "default". Both nodes are shown in "Mems_allowed*". Mems_allowed: 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003 Mems_allowed_list: 0-1 > Andi already mentioned zone_reclaim_mode. ÂYou'll want that set to '0' > if you want allocations to overflow/fallback to off-node without > attempting direct reclaim first. ÂE.g., set vm.zone_reclaim_mode = 0 in > your /etc/sysctl.conf and reload via 'sysctl -p' if you want it to > stick. > I set zone_reclaim_mode to zero. It is working fine. :-) DD can allocate remaining memory from other node. BTW, I have tried several vanilla kernels and Issue is not visible after 2.6.31. Is there anyway to identify the patch which should have fix this in 2.6.31* trees? Thankx a lot for your support. Tharindu. -- 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
