[lkml]   [1998]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: (reiserfs) Re: Implementing Meta File information in Linux (and a note at the end on current reiserfs status)
Followup to:  <199809031247.WAA16479@vindaloo.atnf.CSIRO.AU>
By author: Richard Gooch <>
In newsgroup:
> > > Of course, if you have large metadata, then you're better off making
> > > each stream as a file in a directory and letting the FS do the work.
> > > The FS code already has one bunch of code to implement growing streams
> > > (files), I think we'd want to leverage that instead of implementing
> > > yet another level of what is effectively file/directory management
> > > inside the FS.
> To clarify: I see two situations. The first is where you have a small
> number of secondary streams of small size which don't grow much. Here
> a single file can suffice.
> The second case is where these assumptions break down, and in that
> case I think each stream belongs in a file. A userspace API is written
> to allow you to deal with the dataset as a single object. For
> consistency, even where the above assumptions hold, it's probably
> better to use one file per stream.
> I see directories being excellent placeholders for grouping
> metadata. With reiserFS, this userspace implementation will be very
> fast, so it's the logical way to go, IMO.

For the small data objects (i.e. "resources"), it seems that using a
standard database library like gdbm or db is appropriate.

PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74
See for web page and full PGP public key
I am Bahá'í -- ask me about it or see
"To love another person is to see the face of God." -- Les Misérables

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.114 / U:0.028 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site