> On Sun, 13 Jun 2010, KOSAKI Motohiro wrote: > > > I have no objection because it's policy matter. but if so, dump_tasks() > > should display mem_allowed mask too, probably. > > You could, but we'd want to do that all under cpuset_buffer_lock so we > don't have to allocate it on the stack, which can be particularly lengthy > when the page allocator is called. Probably we don't need such worry. becuase a stack overflow risk depend on deepest call path. That's said, if out_of_memory() was called, page allocator did called try_to_free_pages() at first. try_to_free_pages() have much deeper stack rather than out_of_memory(). -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>