60 likes | 339 Views
Net100 year 1 leftovers (proposal):. PSC none ORNL router access to SNMP data (besides edge routers) OC48 testing LBNL NWS interfacing -- mute?. Net100 year 2 proposal milestones. LBNL. - NTAF improvements - tool development - autotune grid apps - impact of tuned apps
E N D
Net100 year 1 leftovers (proposal): • PSC • none • ORNL • router access to SNMP data (besides edge routers) • OC48 testing • LBNL • NWS interfacing -- mute?
Net100 year 2 proposal milestones LBNL - NTAF improvements - tool development - autotune grid apps - impact of tuned apps - impact of parallel streams - alternate protocol analysis - NWS/NAB improvements ? - integrate with other monitoring projects • PSC • NAOS in multi-site dist. App. ? • Instruments and enhancements • standardization process • other OS’s • remote access mechanism • ORNL • Net100 and HPSS protocols • ECN tuning/testing • other OS’s • include statistical sampling of netlets • multipath routing
Net100 year 2 -- needs • Additional analysis of TCP tuning options • selecting thresholds/values (AIMD, max_ssthresh, reorder) • parallel tuning (# of streams, buffer size, wrappers, other tuning) • using NTAF data to make tuning decisions • NTAF tools for characterizing paths • Determining # of streams and size • Distinguish type of loss? (wireless) • Web100 tuning/tracing scalability study • WAD/kernel tuning extensions • del ACK, reordering, caching (initial window), burst mgt., initial scale factor, pacing options • DRS ? • Can loss be anticipated? ( ss tuning ? Vegas ? ?) • useable tuning package and demonstrated results • other OS’s -- AIX ? *BSD? Compaq? Irix? ? • 10GigE/OC48/OC192 and wireless tuning • interdependencies ? ORNL/PSC/LBNL
WAD extensions Some Possible WAD algorithms (Mathis 11/27/01) Notes Description DUP threshold (out of order resiliance) intial receive window/scale factor cwnd high limit D ssthresh low limit d Set initial cwnd d Set restart window (e.g. after a timeout) Set initial ssthresh D AIMD constants (also virtual MSS) d Force MTU down (pseudo pacing) K Spin pacing KKn True pacing (open research question) Explicit burst size limits KD Force MTU up (and IP fragmentation) Force client "from" address Force per connection routing (pseudo redirects) Force per connection source route option (LSRR) a Use multiple connections a Negotiate application copy buffer size Set socket "ready" thresholds K Interrupt coalescing parameters K ACK frequency/(long) delayed ack/delayed window parameters d Nagle parameters K In situ path diagnostics to run under any app (diagnostic anti-tune) d=dangerous to the net or other applications D=very dangerous to the net or other applications (All may have adverse affects to the local host or application) K=Requires non-trivial kernel support a=requires WAD to Application API (all other are WAD to kernel) (all assume some kernel support) n=Not really a workaround (e.g. should be in TCP) WAD tuning for grid? Wireless: MSS reduction expo backoff cancel other ?
ORNL year 2 • TCP tuning analysis (internet, ns, NISTnet) • WAD/kernel extensions • NTAF integration • Other OS web100 ? (AIX *BSD) • Nagi • Integration of neural network predictors with previous ones using projective fusers • Analysis and testing of two- and three-stream TCP; atou and net100 implementation • Analysis of time-scales of measurements and statistical estimators for transport control • Integration of statistical estimators into transport control loop at the appropriate time-scales
Net100 year 2 outreach • Papers: ? • End of FY report • Talks: ? • Web pages • Interactions with other groups (e2e, Esnet, app’s, MICS networking)