Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262589AbVAPTkV (ORCPT ); Sun, 16 Jan 2005 14:40:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262590AbVAPTkU (ORCPT ); Sun, 16 Jan 2005 14:40:20 -0500 Received: from opersys.com ([64.40.108.71]:15634 "EHLO www.opersys.com") by vger.kernel.org with ESMTP id S262589AbVAPTkM (ORCPT ); Sun, 16 Jan 2005 14:40:12 -0500 Message-ID: <41EAC4C5.7@opersys.com> Date: Sun, 16 Jan 2005 14:47:17 -0500 From: Karim Yaghmour Reply-To: karim@opersys.com Organization: Opersys inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en, fr, fr-be, fr-ca, fr-fr MIME-Version: 1.0 To: Christoph Hellwig CC: Roman Zippel , Andi Kleen , Nikita Danilov , linux-kernel@vger.kernel.org, Tom Zanussi Subject: Re: 2.6.11-rc1-mm1 References: <20050114002352.5a038710.akpm@osdl.org> <20050114103836.GA71397@muc.de> <41E7A7A6.3060502@opersys.com> <41E8358A.4030908@opersys.com> <20050116161437.GA26144@infradead.org> In-Reply-To: <20050116161437.GA26144@infradead.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1421 Lines: 41 Hello Christoph, Christoph Hellwig wrote: > Why would you want anything but read access? Fine, we can put it read-only, we'll drop the "mode" field. > I think random access is overkill. Keeping the code simple is more > important and user-space can post-process it. it's overkill if you're thinking in terms of kbs or mbs of data. it isn't if you're looking at gbs and 100gbs. please read my other posting as to who is using this and how. but regardless of access, you have to have some way of telling relayfs of the size of the channel you want. bufsize, nbufs just tell relayfs the size of the buffers you want and how many buffers there are in the ring. both of which are really basic to any sort of buffering scheme. > Auto-resizing sounds like a really bad idea. Ok, it will go. > And why can't you do this from that code? It just needs an initcall-like > thing that runs after mounting of relayfs. Ok, we'll leave it to the caller to do a relay_write() with his init-bufs at startup. 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 - 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/