Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030187AbWHQRYG (ORCPT ); Thu, 17 Aug 2006 13:24:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030192AbWHQRYG (ORCPT ); Thu, 17 Aug 2006 13:24:06 -0400 Received: from e33.co.us.ibm.com ([32.97.110.151]:47799 "EHLO e33.co.us.ibm.com") by vger.kernel.org with ESMTP id S1030187AbWHQRYE (ORCPT ); Thu, 17 Aug 2006 13:24:04 -0400 Subject: Re: [ckrm-tech] [RFC][PATCH 5/7] UBC: kernel memory accounting (core) From: Dave Hansen To: rohitseth@google.com Cc: Alan Cox , Rik van Riel , Andi Kleen , ckrm-tech@lists.sourceforge.net, Linux Kernel Mailing List , Kirill Korotaev , Christoph Hellwig , Andrey Savochkin , devel@openvz.org, hugh@veritas.com, Ingo Molnar , Pavel Emelianov In-Reply-To: <1155835003.14617.45.camel@galaxy.corp.google.com> References: <44E33893.6020700@sw.ru> <44E33C8A.6030705@sw.ru> <1155754029.9274.21.camel@localhost.localdomain> <1155755729.22595.101.camel@galaxy.corp.google.com> <1155758369.9274.26.camel@localhost.localdomain> <1155774274.15195.3.camel@localhost.localdomain> <1155824788.9274.32.camel@localhost.localdomain> <1155835003.14617.45.camel@galaxy.corp.google.com> Content-Type: text/plain Date: Thu, 17 Aug 2006 10:23:21 -0700 Message-Id: <1155835401.9274.64.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 581 Lines: 16 On Thu, 2006-08-17 at 10:16 -0700, Rohit Seth wrote: > > That said, it sure is simpler to implement, so I'm all for it! > > hmm, not sure why it is simpler. When you ask the question, "which container owns this page?", you don't have to look far, nor is it ambiguous in any way. It is very strict, and very straightforward. -- Dave - 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/