lkml.org 
[lkml]   [2000]   [Mar]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: NWFS Source Code Posted at 207.109.151.240
    In message <38E25AE9.5D59289@timpanogas.com>, "Jeff V. Merkey" writes:
    >
    >
    > Steve Dodd wrote:
    >
    > > AIUI [0], Al Viro, Stephen Tweedie, and a number of others have some
    > > interesting plans for the block device layer, buffer cache and page cache,
    > > and the interactions between them and with the VFS -- for 2.5. I assume
    > > they're busy with tidying up 2.4pre loose ends at the moment, but hopefully
    > > after 2.4 is out the door and stable there will be some discussion of the
    > > planned changes on linux-fsdevel. It sounds (I've not looked at your code yet)
    > > like your input would be useful when that happens. An I/O system that meets
    > > everyone's needs for 2.6 would be a great goal..
    > >
    > > BTW, regarding your comments about Linux documentation - have you looked at
    > > the work Alan Cox is doing on this yet?
    > >
    >
    > Yes, i've looked at Alan's Documentation stuff. And as always, Alan's
    > work is absolutely excellent -- however, what's really needed is
    > something like NT puts out with their IFS Kits, a sample VFS code
    > example for a NULL file system for folks who are porting to Linux.

    If you'd like a stackable f/s example, look at my work called "fist". It
    includes stackable file system templates and examples derived from it: a
    wrapper file system called wrapfs, and example such as ro13fs, cryptfs, and
    more:

    http://www.cs.columbia.edu/~ezk/research/fist/

    At the moment, the linux kernel needs very small passive patches to support
    loadable stackable modules. I've submitted those and hope they will be
    incorporated before 2.4 is out officially.

    I also plan to submit my template to Linus etc. for inclusion. The
    templates work just like lofs, but they are also an excellent way of
    learning how to write stackable file systems (and would nicely complement
    any improved documentation), and deriving new file systems out of it.

    > Would cut down on time along with an "oh shit" list of interface issues
    > to watch out for. Richard Gooch did a decent job on the vfs.txt file
    > (it was better than nothing). We need more though to get on par with
    > NT.
    >
    > Jeff

    Erez.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

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