Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262843AbUKRSmH (ORCPT ); Thu, 18 Nov 2004 13:42:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262857AbUKRSlH (ORCPT ); Thu, 18 Nov 2004 13:41:07 -0500 Received: from clock-tower.bc.nu ([81.2.110.250]:40681 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id S262856AbUKRSeM (ORCPT ); Thu, 18 Nov 2004 13:34:12 -0500 Subject: Re: [PATCH] [Request for inclusion] Filesystem in Userspace From: Alan Cox To: Linus Torvalds Cc: Miklos Szeredi , hbryan@us.ibm.com, akpm@osdl.org, linux-fsdevel@vger.kernel.org, Linux Kernel Mailing List , pavel@ucw.cz In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1100798975.6018.26.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 18 Nov 2004 17:29:38 +0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 633 Lines: 15 > I really do believe that user-space filesystems have problems. There's a > reason we tend to do them in kernel space. > > But limiting the outstanding writes some way may at least hide the thing. Possibly dumb question. Is there a reason we can't have a prctl() that flips the PF_* flags for a user space daemon in the same way as we do for kernel threads that do I/O processing ? - 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/