Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756168Ab2F2PtI (ORCPT ); Fri, 29 Jun 2012 11:49:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:5216 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752881Ab2F2PtG (ORCPT ); Fri, 29 Jun 2012 11:49:06 -0400 Message-ID: <4FEDCE2B.9010908@redhat.com> Date: Fri, 29 Jun 2012 11:47:55 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Andrea Arcangeli CC: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Hillf Danton , Dan Smith , Peter Zijlstra , Linus Torvalds , Andrew Morton , Thomas Gleixner , Ingo Molnar , Paul Turner , Suresh Siddha , Mike Galbraith , "Paul E. McKenney" , Lai Jiangshan , Bharata B Rao , Lee Schermerhorn , Johannes Weiner , Srivatsa Vaddagiri , Christoph Lameter , Alex Shi , Mauricio Faria de Oliveira , Konrad Rzeszutek Wilk , Don Morris , Benjamin Herrenschmidt Subject: Re: [PATCH 10/40] autonuma: mm_autonuma and sched_autonuma data structures References: <1340888180-15355-1-git-send-email-aarcange@redhat.com> <1340888180-15355-11-git-send-email-aarcange@redhat.com> In-Reply-To: <1340888180-15355-11-git-send-email-aarcange@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1763 Lines: 48 On 06/28/2012 08:55 AM, Andrea Arcangeli wrote: You tell us when the data structures are not allocated, but you do not tell us how the data structures is used, or what the fields inside the data structures mean. This makes it very hard for other people to figure out the code later. Please document these kinds of things properly. > +/* > + * Per-mm (process) structure dynamically allocated only if autonuma > + * is not impossible. This links the mm to scan into the > + * knuma_scand.mm_head and it contains the NUMA memory placement > + * statistics for the process (generated by knuma_scand). > + */ > +struct mm_autonuma { > + /* list node to link the "mm" into the knuma_scand.mm_head */ > + struct list_head mm_node; > + struct mm_struct *mm; > + unsigned long mm_numa_fault_pass; /* zeroed from here during allocation */ > + unsigned long mm_numa_fault_tot; > + unsigned long mm_numa_fault[0]; > +}; > +/* > + * Per-task (thread) structure dynamically allocated only if autonuma > + * is not impossible. This contains the preferred autonuma_node where > + * the userland thread should be scheduled into (only relevant if > + * tsk->mm is not null) and the per-thread NUMA accesses statistics > + * (generated by the NUMA hinting page faults). > + */ > +struct task_autonuma { > + int autonuma_node; > + /* zeroed from the below field during allocation */ > + unsigned long task_numa_fault_pass; > + unsigned long task_numa_fault_tot; > + unsigned long task_numa_fault[0]; > +}; -- All rights reversed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/