Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Lazy Receiver Processing (LRP): A Network Subsystem Architecture for Server Systems Peter Druschel & Gaurav Banga OSDI ’96 Song, yong-joo System Software Lab, EECS, KAIST 16, November 2000 This paper provides good knowledge of Network Subsystem and fresh approach. Contents Introduction BSD Architecture LRP Early demultiplexing Lazy protocol processing UDP/TCP Experiment Conclusion & Critique 3 Introduction Resource management issue Fairness! under heavy load Cf. improve latency, use full bandwidth 4 BSD Architecture Lower layer, higher priority Invest in dropped packet Lack of effective load shedding All packet in one IP queue Eager receiver processing Lack of traffic separation Use CPU time of Interrupted process Inappropriate resource accounting 5 LRP IP Queue -> per socket Queue NI demultiplex packets NI demux Soft demux Protocol processing at the priority of receiving process lazily 6 LRP ( cont’d ) Early demultiplexing problem Still livelock – control msg. or corrupted data Context switching Fair resource allocation Lazy Receiver Processing Reduced context switching Increased memory locality 7 LRP - TCP Reliable, flow-controlled -> LRP cannot Asynchronous receiver processing RR at the priority of app. of associated socket CPU time is charged to associated process Implementation : extra Kernel thread small extra memory overhead 8 Experiment setup Sun SPARC – 60MHz, 32MB 155Mbit/s ATM LAN SBA-200 network adaptor ( include i960 ) Modified 4.4BSD-Lite Metric Throughput Latency 9 Result 10 Conclusion LRP architecture Early demultiplex Lazy receiver processing Case of TCP Reduced context switching Enhanced throughput, latency under heavy load 11 Critique NI channel Queue length decision Measuring Latency with Same or higher priorty process Stable under overload? Apply to QoS