1 / 8

Storage WG Update

This update provides information on the Genesis and History of the TinyOS Storage Working Group, its current status, key issues being addressed, early focus areas, intersection with the core TinyOS, and future plans for low-level system interfaces, high-level storage-backed data structures, and developer productivity. Join the Storage Working Group to help shape the future of TinyOS storage!

dantonio
Download Presentation

Storage WG Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Storage WG Update Prabal Dutta On behalf of Junzhao Du, Deepak Ganesan, Kevin Klues, Ajay Martin, Gaurav Mather, David Moss, Manju Rajashekhar

  2. Genesis and History • Proposed by Deepak Ganesan at the TinyOS BOF during Sensys’06 • Initial membership policy • People responsive to the “Request for Participation” • Weekly Telecons in 2007 • 3/30, 4/6, 4/13, 4/20, 5/4 … • Wiki • http://tinyos.cs.berkeley.edu/storage • Mailing List • tinyos-storage@millennium.berkeley.edu

  3. Status • In May ’07, nearly all of the students graduated and we lost critical mass! • No motivating applications are driving progress in the storage working group

  4. 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.”

  5. Key Issues • Performance vs. Portability • Enumerate the tradeoffs; Find a balance • Richer set of storage objects • Stream, index, queue, stack, dictionary • Checkpoints, rollbacks, and compaction • A common framework • Sharing a volume among several objects • Simple interleaving? Layered storage stacks?

  6. Early Focus • TEP 128 • Platform-independent storage abstractions • Revisiting volumes • Direct storage • TEP 129 • Basic Platform-Independent Non-volatile Storage Layers • Implementing platform-independent versions of Config, Log, Block, Stream, Index, Queue, Stack, Dictionary • TEP *** • Common framework for checkpointing and rollback

  7. Intersection with Core • At the storage abstractions and interfaces • Volume • Config • Log • Block • New storage abstractions below, next to, or above? • Direct access • Volume settings • Layered, interleaved log • Lots of discussion and debate about the basic interfaces • Performance vs Portability • Generality vs Specificity • Will resolve differences through implementation and evaluation

  8. Going Forward • Low-level system interfaces • Bedrock of the storage system • Getting them right is important • High-level, storage-backed, data structures • Hide low-level details • Enable greater developer productivity (e.g. Java Collections framework) • …And the messy middle • Help shape the future of TinyOS storage by joining the Storage Working Group! • Or we could just build stuff that uses storage

More Related