From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: [PATCH] [Request for inclusion] Filesystem in Userspace Date: Thu, 18 Nov 2004 17:29:38 +0000 Message-ID: <1100798975.6018.26.camel@localhost.localdomain> References: Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Miklos Szeredi , hbryan@us.ibm.com, akpm@osdl.org, linux-fsdevel@vger.kernel.org, Linux Kernel Mailing List , pavel@ucw.cz Return-path: 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 To: Linus Torvalds In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org > 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 ?