Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752910Ab1BVBxl (ORCPT ); Mon, 21 Feb 2011 20:53:41 -0500 Received: from e4.ny.us.ibm.com ([32.97.182.144]:34187 "EHLO e4.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752098Ab1BVBxl (ORCPT ); Mon, 21 Feb 2011 20:53:41 -0500 Subject: [PATCH 0/5] fix up /proc/$pid/smaps to not split huge pages To: linux-kernel@vger.kernel.org Cc: linux-mm@kvack.org, Michael J Wolf , Andrea Arcangeli , akpm@osdl.org, Dave Hansen From: Dave Hansen Date: Mon, 21 Feb 2011 17:53:38 -0800 Message-Id: <20110222015338.309727CA@kernel> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1219 Lines: 30 Andrew, these have gone through a couple of review rounds. Can they have a spin in -mm? -- I'm working on some more reports that transparent huge pages and KSM do not play nicely together. Basically, whenever THP's are present along with KSM, there is a lot of attrition over time, and we do not see much overall progress keeping THP's around: http://sr71.net/~dave/ibm/038_System_Anonymous_Pages.png (That's Karl Rister's graph, thanks Karl!) However, I realized that we do not currently have a nice way to find out where individual THP's might be on the system. We have an overall count, but no way of telling which processes or VMAs they might be in. I started to implement this in the /proc/$pid/smaps code, but quickly realized that the lib/pagewalk.c code unconditionally splits THPs up. This set reworks that code a bit and, in the end, gives you a per-map count of the numbers of huge pages. It also makes it possible for page walks to _not_ split THPs. -- 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/