From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail203.messagelabs.com (mail203.messagelabs.com [216.82.254.243]) by kanga.kvack.org (Postfix) with ESMTP id 9243F6B0047 for ; Tue, 28 Apr 2009 06:14:39 -0400 (EDT) Date: Tue, 28 Apr 2009 12:18:51 +0200 From: Andi Kleen Subject: Re: [PATCH 5/5] proc: export more page flags in /proc/kpageflags Message-ID: <20090428101851.GM27382@one.firstfloor.org> References: <84144f020904280219p197d5ceag846ae9a80a76884e@mail.gmail.com> <20090428092918.GC21085@elte.hu> <20090428183237.EBDE.A69D9226@jp.fujitsu.com> <20090428093833.GE21085@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090428093833.GE21085@elte.hu> Sender: owner-linux-mm@kvack.org To: Ingo Molnar Cc: KOSAKI Motohiro , Pekka Enberg , Andi Kleen , Wu Fengguang , Steven Rostedt , =?utf-8?B?RnLpppjpp7tpYw==?= Weisbecker , Larry Woodman , Peter Zijlstra , Eduard - Gabriel Munteanu , Andrew Morton , LKML , Matt Mackall , Alexey Dobriyan , "linux-mm@kvack.org" List-ID: > But it has to be expressed in one framework that cares about the > totality of the kernel - not just these splintered bits of Can you perhaps expand a bit what code that framework would provide to kpageflags? As far as I can see it only needs a ->read callback from somewhere and I admit it's hard to see for me how that could share much code with anything else. -Andi -- ak@linux.intel.com -- Speaking for myself only. -- 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/ . Don't email: email@kvack.org