From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx123.postini.com [74.125.245.123]) by kanga.kvack.org (Postfix) with SMTP id CA5216B007E for ; Wed, 22 Feb 2012 18:00:12 -0500 (EST) Date: Wed, 22 Feb 2012 15:00:10 -0800 From: Andrew Morton Subject: Re: [RESEND][PATCH] Mark thread stack correctly in proc//maps Message-Id: <20120222150010.c784b29b.akpm@linux-foundation.org> In-Reply-To: References: <4F32B776.6070007@gmail.com> <1328972596-4142-1-git-send-email-siddhesh.poyarekar@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Siddhesh Poyarekar Cc: KOSAKI Motohiro , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Alexander Viro , linux-fsdevel@vger.kernel.org, Jamie Lokier , Mike Frysinger On Tue, 21 Feb 2012 09:54:04 +0530 Siddhesh Poyarekar wrote: > Stack for a new thread is mapped by userspace code and passed via > sys_clone. This memory is currently seen as anonymous in > /proc//maps, which makes it difficult to ascertain which mappings > are being used for thread stacks. This patch uses the individual task > stack pointers to determine which vmas are actually thread stacks. > > The display for maps, smaps and numa_maps is now different at the > thread group (/proc/PID/maps) and thread (/proc/PID/task/TID/maps) > levels. The idea is to give the mapping as the individual tasks see it > in /proc/PID/task/TID/maps and then give an overview of the entire mm > as it were, in /proc/PID/maps. > > At the thread group level, all vmas that are used as stacks are marked > as such. At the thread level however, only the stack that the task in > question uses is marked as such and all others (including the main > stack) are marked as anonymous memory. Please flesh this description out with specific examples of the before-and-after contents of all the applicable procfs files. This way we can clearly see the proposed interface changes, which is the thing we care most about with such a patch. The patch itself has been utterly and hopelessly mangled by gmail. Please fix that up when resending (as a last resort: use a text/plain attachment). -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org