Storage WG Update.pptVIP

Storage WG Update Prabal Dutta On behalf of Junzhao Du, Deepak Ganesan, Kevin Klues, Ajay Martin, Gaurav Mather, David Moss, Manju Rajashekhar 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 /storage Mailing List tinyos-storage@ 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 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.” 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? 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 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 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 Collectio