From: Al Boldi Subject: Re: Allocation strategy - dynamic zone for small files Date: Tue, 14 Nov 2006 18:43:39 +0300 Message-ID: <200611141843.39745.a1426z@gawab.com> References: <1163426218.3343.10.camel@avishay.fsl.cs.sunysb.edu.fsl.cs.sunysb.edu> <200611141421.09823.a1426z@gawab.com> <20061114142553.GB30961@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from [212.33.187.9] ([212.33.187.9]:50048 "EHLO raad.intranet") by vger.kernel.org with ESMTP id S966026AbWKNPkg (ORCPT ); Tue, 14 Nov 2006 10:40:36 -0500 To: Theodore Tso In-Reply-To: <20061114142553.GB30961@thunk.org> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Theodore Tso wrote: > On Tue, Nov 14, 2006 at 02:21:09PM +0300, Al Boldi wrote: > > > etc. When I pointed out the system call overhead that would result > > > since instead of an open, read, close to read /etc/inetd.conf, you > > > would now need perhaps a hundred or more system calls do the > > > opendir/readir loop, and then individually opening, reading, and > > > closing each file, Hans had a solution ---- > > > > I have a different solution. > > > > Plugins into the VFS that handle special situations. > > > > I could do something like this manually in userland via loop/FUSE, but a > > more integrated solution could prove more useful. > > So now an application that needs to read/write 16 byte files > efficiently needs to write a kernel module that gets logged into the > VFS?!? And we have to trust our system stability to an application > writer to not introduce any bugs into the VFS plugin that might cause > a system panic? An API would probably be in order. > What's the advantage of using smallish ~16 byte files in this case? > If it's ease of application programming, that just got flushed down > the drain; writing kernel modules is harder, because (a) the > compile/edit/debug cycle, if you screw up, crashes your system, and > (b) it requires root privs to install the application. > > What exactly is the problem that people are trying to solve with > trying to get the kernel involved with storing tiny individual datums, > as opposed to simply asking the application to store all of these > objects in a userland database, where the object layout can be > optimized for the application's needs? Performance due to non-redundancy. > This really feels like a fragile technological hack looking for a > problem to solve.... Or a desire to let people choose what they want. Think freedom... Thanks! -- Al