Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262046AbVAQQQj (ORCPT ); Mon, 17 Jan 2005 11:16:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262163AbVAQQQj (ORCPT ); Mon, 17 Jan 2005 11:16:39 -0500 Received: from e33.co.us.ibm.com ([32.97.110.131]:32478 "EHLO e33.co.us.ibm.com") by vger.kernel.org with ESMTP id S262046AbVAQQQb (ORCPT ); Mon, 17 Jan 2005 11:16:31 -0500 From: Tom Zanussi MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16875.61369.54922.114653@tut.ibm.com> Date: Mon, 17 Jan 2005 11:02:49 -0600 To: karim@opersys.com Cc: Roman Zippel , Andi Kleen , Nikita Danilov , linux-kernel@vger.kernel.org, Tom Zanussi Subject: Re: 2.6.11-rc1-mm1 In-Reply-To: <41EADA11.70403@opersys.com> References: <20050114002352.5a038710.akpm@osdl.org> <20050114103836.GA71397@muc.de> <41E7A7A6.3060502@opersys.com> <41E8358A.4030908@opersys.com> <41E899AC.3070705@opersys.com> <41EA0307.6020807@opersys.com> <41EADA11.70403@opersys.com> X-Mailer: VM 7.18 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1504 Lines: 45 Karim Yaghmour writes: > > Hello Roman, > > > What we are dropping for later review: read/write semantics from > user-space. It has to be understood that we believe that this is > a major drawback. For one thing, you won't be able to do something > like: > $ cat /relayfs/xchg/my-file > ~/test-data > > Instead, you will have to write a custom app that does open(), > mmap(), write(). We could still provide a small app/library that > did this automagically, but you've got to admit that nothing > beats the real thing. > Maybe we could use FUSE to provide read()/write() for relayfs files - opening a FUSE relayfs file would open and mmap the actual relayfs file, read() would move around in the buffer using basically the current relayfs read logic moved down into the FUSE filesystem read fileop, and write() could write directly to the buffer... Tom > Also note that there are people who currently use this already, > so there will be some unhappy campers. > > Karim > -- > Author, Speaker, Developer, Consultant > Pushing Embedded and Real-Time Linux Systems Beyond the Limits > http://www.opersys.com || karim@opersys.com || 1-866-677-4546 -- Regards, Tom Zanussi IBM Linux Technology Center/RAS - 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/