From: Hans Reiser <reiser@namesys.com>
To: Martin.Gasthuber@desy.de
Cc: Reiserfs-List@namesys.com
Subject: Re: plugins - examples and (more) docs
Date: Thu, 30 Sep 2004 10:52:35 -0700 [thread overview]
Message-ID: <415C47E3.9010703@namesys.com> (raw)
In-Reply-To: <41556502.6030505@desy.de>
Martin Gasthuber wrote:
> Hi,
>
> for our large storage system holding half a petabyte of experimental
> physics data, we are looking for a new nameservice implementation.
> Roughly this means - just store filenames in a hierarchical fashion
> (as usual) but only store metadata (from the other storage system
> components i.g. disk-cache and tape store) and no real data (this is
> in the cache - one or more times, and the 'real' copy is on tape).
> Right now we have a DB (simple key/value) system with a faked NFS
> server code on top.
> While looking at other ways and making proof of concept implementation
> i 'traped' into reiser4 with the important plugin feature. For our
> system we need 'unique + persistent' IDs for files with the ability to
> map in both directions (name -> id, id -> name), extended attributes
> and virtual files. From what i understand, reading the reiser4 docs
> i've found, all this should be feasible by creating new plugins for
> files and IDs. Because i like 'real' stuff - im' looking for plugin
> example code and more docs related to plugin creation and integration.
> Any idea where i can find that ???
>
> Regards,
> Martin
>
>
You are right that this is doable, for examples see our source code
which is much better commented than the rest of the kernel (disclaimer:
akpm code is better commented than ours).
prev parent reply other threads:[~2004-09-30 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 12:30 plugins - examples and (more) docs Martin Gasthuber
2004-09-30 17:52 ` Hans Reiser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=415C47E3.9010703@namesys.com \
--to=reiser@namesys.com \
--cc=Martin.Gasthuber@desy.de \
--cc=Reiserfs-List@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.