A Power-Aware Network Device Driver in Ad hoc Network Peng Xue Department of Computer Science and Engineering University of Notre Dame
Motivations Energy is limited and important A fact: WNIC consumes as much as 50% of total energy. Routing traffic without control Ad-hoc v.s. Infrastructure Local traffic vs routing traffic Users have no control First WORTS 2005 6/8/2019
Preliminary Knowledge Power Level (mWatts) Time (us) 1500 4500 6000 Stage 1 Stage 2 Stage 3 Stage1: WNIC receives frame from air (1500*8*/(11M*0.7)~1500us). Stage2: OS reads the frame from WNIC, forwards, writes to WNIC Stage3: WNIC sends frame to the air Routing a 1500-byte packet device kernel 1675 1425 1319 First WORTS 2005 6/8/2019
Thesis Save energy by doing admission control at the Wireless Network Interface Card (WNIC ) device driver level Benefits Save energy (WNIC energy + CPU energy ) Improve local performance Problem Routing traffic reduced First WORTS 2005 6/8/2019
A Power-aware Device Driver Distinguish local/routing traffic A concept like Packet filter in Exo-kernel Read headers first (IP, Ethernet) Implement power policies to drop routing packets. Energy fair policy Formula : α = β(1- E), α is dropping rate Flow discrimination First WORTS 2005 6/8/2019
Evaluation Energy WNIC Energy First WORTS 2005 6/8/2019
Evaluation CPU energy Hard to measure, use CPU load Low CPU load, DVS, DFS can be used First WORTS 2005 6/8/2019
Evaluation Local Performance First WORTS 2005 6/8/2019
Drawbacks Worsen the performance of routing Routing traffic drops accordingly Possible energy consumption increase in the sending part Packets get lost… No problem for multimedia but not file transfer First WORTS 2005 6/8/2019
Question and Comments? First WORTS 2005 6/8/2019
Feedback control dropping scheme Y : actual routing traffic throughput. r : throughput the intermediate node wants to support. e : difference between Y and r. u : dropping rate C : controller. First WORTS 2005 6/8/2019
Kernel or Device Driver ? First WORTS 2005 6/8/2019