On 06/28/2012 08:55 AM, Andrea Arcangeli wrote:
This is where the dynamically allocated sched_autonuma structure is being handled. The reason for keeping this outside of the task_struct besides not using too much kernel stack, is to only allocate it on NUMA hardware. So the not NUMA hardware only pays the memory of a pointer in the kernel stack (which remains NULL at all times in that case).
What is not documented is the reason for keeping it at all. What is in the data structure? What is the data structure used for? How do we use it?
+ if (unlikely(alloc_task_autonuma(tsk, orig, node))) + /* free_thread_info() undoes arch_dup_task_struct() too */ + goto out_thread_info;
Oh, you mean task_autonuma, and not sched_autonuma? Please fix the commit message and the subject. -- All rights reversed -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>