Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261855AbVCCPsq (ORCPT ); Thu, 3 Mar 2005 10:48:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261866AbVCCPsq (ORCPT ); Thu, 3 Mar 2005 10:48:46 -0500 Received: from aun.it.uu.se ([130.238.12.36]:3529 "EHLO aun.it.uu.se") by vger.kernel.org with ESMTP id S261855AbVCCPsh (ORCPT ); Thu, 3 Mar 2005 10:48:37 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16935.12745.191707.91582@alkaid.it.uu.se> Date: Thu, 3 Mar 2005 16:48:25 +0100 From: Mikael Pettersson To: Andrew Morton Cc: miklos@szeredi.hu, torvalds@osdl.org, linux-kernel@vger.kernel.org Subject: Re: [request for inclusion] Filesystem in Userspace In-Reply-To: <20050303013203.245c8833.akpm@osdl.org> References: <20050302123123.3d528d05.akpm@osdl.org> <16934.54647.354607.902748@alkaid.it.uu.se> <20050303013203.245c8833.akpm@osdl.org> X-Mailer: VM 7.17 under Emacs 20.7.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1663 Lines: 41 Andrew Morton writes: > Mikael Pettersson wrote: > > > > Andrew Morton writes: > > > Miklos Szeredi wrote: > > > > > > > > Do you have any objections to merging FUSE in mainline kernel? > > > > > > I was planning on sending FUSE into Linus in a week or two. That and > > > cpusets are the notable features which are 2.6.12 candidates. > > > > > > - crashdump seems permanently not-quite-ready > > > > > > - perfctr works fine, but is rather deadlocked because it is > > > similar-to-but-different-from ia64's perfmon, and might not be suitable > > > for ppc64 (although things have gone quiet on the latter front). > > > > perfctr has one API update pending, and then the API should be > > in it final-ish form. David Gibson at IBM has done a ppc64 port, > > which is about ready to be merged, and someone else has just > > started working on a mips port. > > > > That sounds good. Where do we stand now with ia64? Do we just end up > agreeing to differ? I think so, yes. The ia64 perfmon has some features perfctr doesn't have, but my perfctr API changes will allow perfctr to grow its feature list and adapt to HW changes without breaking the API. Its unlikely that perfctr will ever implement everything perfmon does, but multiplexing and overflow sample buffering are two features that should be added at some point. /Mikael - 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/