[Tinyos-Storage WG] Re: Storage WG

[Prabal Dutta]

Hey everyone,

I just approved everybody who had an outstanding request on the
mailing list.  So far, Kevin Klues, David Moss, Ajay Martin, and
Junzhao Du have registered.  It would be great if the rest of us would
register soon so we can start using the list address
(tinyos-storage at millennium.berkeley.edu) instead of a list of e-mail
addresses.

Thanks!

- Prabal

On 4/6/07, Kevin Klues <klueska at gmail.com> wrote:
> I have setup an email list called tinyos-storage and you can now
> subsribe to it here.
>
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-storage
>
> Kevin
>
> On 1/22/07, Deepak Ganesan <dganesan at cs.umass.edu> wrote:
> >
> > Folks,
> >
> > Here is a starting point for the agenda for the Storage WG. We need
> > to generate a brief one-page proposal in about 10 days, and then
> > start discussing regularly to make progress.
> >
> > Here is a draft outline of the charter and the main goals of the WG.
> > Feel free to add or update the outline. Would like to have an initial
> > round of comments by email so that we can send out the 1-page
> > proposal. After that time, we can try to schedule a weekly meeting
> > time to discuss the WG.
> >
> > ------------------------------------------------------------------------
> > -----------------------------------------------
> >
> > Charter: To define storage interfaces and abstractions, reusable non-
> > volatile data structures, interoperability requirements for
> > components that share flash memory, and reference implementations of
> > storage systems.
> >
> > Below are the key issues in a little more detail:
> >
> > + Sharing storage between different applications/objects
> >         - Split storage into volumes and let each application handle its
> > volume however it wants:
> >                 + Volumes: TEP 103 describes an approach for dividing the flash
> > into volumes between different applications
> >                 + Interface VolumeSettings (Blackbook): get information about
> > volume size, read/write units, erase size, etc.
> >         - Interleave objects within a single volume:
> >                 + Object: Capsule describes an approach for interleaving different
> > objects in a single log.
> >
> > + Re-usable non-volatile  data structures/objects:
> >         - Files:
> >         - TEP 103: Large "write once" object, Logs, SmallObject
> >         - Database objects: BDictionary (Blackbook), Stream, Index, Queue
> > (Capsule),
> >
> > + Support for checkpointing and rollback (for hibernation or recovery
> > from node failure)
> >
> > Timeline:
> >
> > - Feb/March/April: Discuss and finalize interfaces
> >         + the goal here would be to decide on the abstractions for sharing
> > storage, data structures and support for checkpointing/rollback
> > - May/June/July: Reference implementation
> >         + would be good to have two or more reference implementations that
> > port the systems that we have already built to the interfaces that we
> > decide to use
> > - July/Aug/Sept: Performance evaluation
> >
> >
> > References (alphabetical):  feel free to add to the list
> >
> > Blackbook File System
> > http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/2006-
> > November/001516.html
> >
> > Capsule: Object Storage System
> > http://sensors.cs.umass.edu/projects/capsule/
> >
> > ELF: Log structured Flash file system
> > http://mantis.cs.colorado.edu/media/sensys_elf_external.pdf
> >
> > FlashDB:
> > http://research.microsoft.com/research/pubs/view.aspx?tr_id=1214
> >
> > Matchbox:
> > http://www.tinyos.net/tinyos-1.x/doc/matchbox.pdf
> >
> > Microhash: Efficient index structure for flash memory
> > http://www.cs.ucr.edu/~vana/microhash.pdf
> >
> > TEP 103:
> > http://www.tinyos.net/tinyos-2.x/doc/html/tep103.html
> >
> > TINX: Tiny Index
> > http://graphics.stanford.edu/projects/lgl/papers/mrl-tinx-06/mrl-
> > tinx-06.pdf
> >
> > thanks
> > Deepak
> >
>
>
> --
> ~Kevin
>