Cost of prefetch at disk in batch system \-- congestion \-- metrics \--
mitigation

Examination in depth of the entire data path

AUGMENT JOB SCHEDULERS TO ASSIST WITH DATA PLACEMENT-STAGING-PREFETCH

\- bRING BACK ibm jcl (FOR PARALLEL APPS)

hOW DO WE LEVERAGE HYBRID DEVICES FOR MORE THAN POWER; PERFORMANCE,
PERSISTENCE, FAULT TOLERANCE, \...

HIGHER AMOUNTS OF flash DO WHAT ALONG THESE LINES?

sTILL HAVE NOT MUCH ADDRESSING THE NUMBER OF STORAGE DEVICES COMING; BE
AFRAID, BE VERY AFRAID?

FAULT TOLERANCE IMPACT AND ISSUES

cAN\'T MJUST INCREASE ACTUATORS WITHOUT ALSO INCREASING BANDWIDTH

dOES THE COMMODITIZATION OF ssd CHANGE ALLOCATION PARADIGMS? wHAT IS THE
RANGE OF THESE POTENTIAL PARADIGMS? iNTEREST IN LEVERAGING THIS

hOW TO DEAL WITH THE LIMITED WRITE LIFE OF flash

BANDWIDTH

iNJECT io SEMANTICS INTO hpcs AND RESEARCH LANGUAGES

A COMPILER FOR STORAGE AND i/o and data structures

compiling for target i/o platform, how to migrate to

new architecture? just recompile.

info flow up and down stack. use grey-box to demonstrate value of
vertical knowledge to motivate future standard change

iS FILE i/o SHARED MEMORY

cAN WE LOOK AT MEMORY PARADIGM RESEARCH TO INFLUENCE I/O?

ibm RULES! as400

tRACE INFORMATION NEEDS COME WITH GOALS OF THE APP/EFFORT

rETHINK THE STACK, PROMOTE SEMANTIC INTERPRETATION TO HIGHERL LEVELS

PUSH THINGS DOWN TO

JUST TAKE A FRESH LOOK AT THE WHOLE STACK

EVEN UP INTO THE APPLICATION

TRACES AT DIFFERENT LEVELS, RELATED

wE WANT ACCESS METHODS {ivqrtA-z\*-AND-ALL-OTHERCHARS}METHODS

SEMANTICS OF INDICES \-- INTELLIGENCE AND

CONTENT ADDRESSABLE, PERSISTENT STORE, SHARABLE AT THE ENTERPRISE (ivp
EX-NODES)

pROVABLY CORRECT, PROVABLY PERFORMANT SYSTEMs (SYSTEMS IS ALL THE
COMPONENTS, REMEMBER?)

hOW DO YOU TAKE SOMETHING SOLID AND RETAIN THAT THROUGH IT\'S DEPLOYMENT

FAULT ANALYSIS FROM EXTERNAL SOURCES

AGING, VALIDATION OVER DATA LIFETIME

PRO-ACTIVE SOLUTIONS

END-TO-END SOLUTIONS (IT\'S A SYSTEM, REMEMBER?)

END-TO-END ERROR ANALYSIS

a CURVES AND BARRIERS EXAM OF CURRENT TECHNOLOGY

ARCHIVE FOLKS LOOKING AT THIS

uSE LOCAL COMPUTE NODE TO EXTEND THE STORAGE HIERARCHY

LOCAL DISK STAGING FOR GLOBAL STORE

more dialogue btwn groups; too often, independent discovery and
redundant

fixing of same problems

\- need open shared bug tracking system

richer movement of app specific knowledge down through layers of system

\- mpi exposes only simple types

hard time working w/ closed source file systems (i.e. gpfs), labs use
gpfs, academics research using pvfs2

\- open standards benefit both open and proprietary source projects

\- alternative leads to research funds spent on support

\- standards evolution is slow (e.g. posix extensions)

\- why standardize on posix? make new national lab standard. but legacy
of posix too powerful. and lab needs external cooperation to ensure
adoptation as well as correctness

\- hpc extensions for posix like real-time extensions previously.
working group has been formed; pushing extensions proving difficult

need global pattern recognition across parallel app (not just w/in
single node)

skip kernel - do everything in user space

standards fundamentally hinder innovation

\- use parallel branches: one working w/in system; one redefining it