From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265065AbUD3GSR (ORCPT ); Fri, 30 Apr 2004 02:18:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261744AbUD3GSR (ORCPT ); Fri, 30 Apr 2004 02:18:17 -0400 Received: from phoenix.infradead.org ([213.86.99.234]:56850 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S265065AbUD3GR5 (ORCPT ); Fri, 30 Apr 2004 02:17:57 -0400 Date: Fri, 30 Apr 2004 07:17:50 +0100 From: Christoph Hellwig To: Rik van Riel Cc: Erik Jacobson , Paul Jackson , chrisw@osdl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Process Aggregates (PAGG) support for the 2.6 kernel Message-ID: <20040430071750.A8515@infradead.org> Mail-Followup-To: Christoph Hellwig , Rik van Riel , Erik Jacobson , Paul Jackson , chrisw@osdl.org, linux-kernel@vger.kernel.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from riel@redhat.com on Thu, Apr 29, 2004 at 05:20:38PM -0400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > I suspect there's a rather good chance of merging a common > PAGG/CKRM infrastructure, since they pretty much do the same > thing at the core and they both have different functionality > implemented on top of the core process grouping. Still doesn't make a lot of sense. CKRM is a huge cludgy beast poking everywhere while PAGG is a really small layer to allow kernel modules keeping per-process state. If CKRM gets merged at all (and the current looks far to horrible and the gains are rather unclear) it should layer ontop of something like PAGG for the functionality covered by it.