Uploaded bymathieu_lacage
1,079 views

ns-3: History and Future

This document provides an overview of the history and future of the ns-3 network simulator project. It discusses how the project originated from multiple partners with different goals and requirements, including real-code integration, emulation, education, wireless modeling, and long-term sustainability. A key challenge was developing an open source community to support ongoing maintenance of the large and complex codebase. The document outlines how ns-3 addressed this by adopting an incremental development process and gaining community involvement and support over time.

Embed presentation

Downloaded 94 times
1 / 143
2 / 143
3 / 143
4 / 143
5 / 143
6 / 143
7 / 143
8 / 143
9 / 143
10 / 143
11 / 143
12 / 143
13 / 143
14 / 143
15 / 143
16 / 143
17 / 143
18 / 143
19 / 143
20 / 143
21 / 143
22 / 143
23 / 143
24 / 143
25 / 143
26 / 143
27 / 143
28 / 143
29 / 143
30 / 143
31 / 143
32 / 143
33 / 143
34 / 143
35 / 143
36 / 143
37 / 143
38 / 143
39 / 143
40 / 143
41 / 143
42 / 143
43 / 143
44 / 143
45 / 143
46 / 143
47 / 143
48 / 143
49 / 143
50 / 143
51 / 143
52 / 143
53 / 143
54 / 143
55 / 143
56 / 143
57 / 143
58 / 143
59 / 143
60 / 143
61 / 143
62 / 143
63 / 143
64 / 143
65 / 143
66 / 143
67 / 143
68 / 143
69 / 143
70 / 143
71 / 143
72 / 143
73 / 143
74 / 143
75 / 143
76 / 143
77 / 143
78 / 143
79 / 143
80 / 143
81 / 143
82 / 143
83 / 143
84 / 143
85 / 143
86 / 143
87 / 143
88 / 143
89 / 143
90 / 143
91 / 143
92 / 143
93 / 143
94 / 143
95 / 143
96 / 143
97 / 143
98 / 143
99 / 143
100 / 143
101 / 143
102 / 143
103 / 143
104 / 143
105 / 143
106 / 143
107 / 143
108 / 143
109 / 143
110 / 143
111 / 143
112 / 143
113 / 143
114 / 143
115 / 143
116 / 143
117 / 143
118 / 143
119 / 143
120 / 143
121 / 143
122 / 143
123 / 143
124 / 143
125 / 143
126 / 143
127 / 143
128 / 143
129 / 143
130 / 143
131 / 143
132 / 143
133 / 143
134 / 143
135 / 143
136 / 143
137 / 143
138 / 143
139 / 143
140 / 143
141 / 143
142 / 143
143 / 143
ns-3: History and Future Mathieu Lacage March, 24th 2012 Lacage ns-3: History and Future March 2012 1 / 27
Outline Introduction Packet Object Framework Conclusion Lacage ns-3: History and Future March 2012 2 / 27
How the project came to be Lacage ns-3: History and Future March 2012 3 / 27
How the project came to be Multiple partners: Lacage ns-3: History and Future March 2012 3 / 27
How the project came to be Multiple partners: NSF-funded: UWA, GT, ISI Lacage ns-3: History and Future March 2012 3 / 27
How the project came to be Multiple partners: NSF-funded: UWA, GT, ISI INRIA-funded: planète Lacage ns-3: History and Future March 2012 3 / 27
How the project came to be Multiple partners: NSF-funded: UWA, GT, ISI INRIA-funded: planète Pulling the project in multiple directions: Real Code Long Term Integration Survival ns-3 Wireless Fast TCP Education Emulation Lacage ns-3: History and Future March 2012 3 / 27
Requirements Lacage ns-3: History and Future March 2012 4 / 27
Requirements Real-code integration, Emulation: Lacage ns-3: History and Future March 2012 4 / 27
Requirements Real-code integration, Emulation: Models must not be too abstract (Node, etc.) Lacage ns-3: History and Future March 2012 4 / 27
Requirements Real-code integration, Emulation: Models must not be too abstract (Node, etc.) Must be transparent to models Lacage ns-3: History and Future March 2012 4 / 27
Requirements Real-code integration, Emulation: Models must not be too abstract (Node, etc.) Must be transparent to models Fast TCP: Lacage ns-3: History and Future March 2012 4 / 27
Requirements Real-code integration, Emulation: Models must not be too abstract (Node, etc.) Must be transparent to models Fast TCP: Memory efficiency of many packets in flight Lacage ns-3: History and Future March 2012 4 / 27
More requirements Lacage ns-3: History and Future March 2012 5 / 27
More requirements Education: Lacage ns-3: History and Future March 2012 5 / 27
More requirements Education: Must be easy to use for students Lacage ns-3: History and Future March 2012 5 / 27
More requirements Education: Must be easy to use for students Wireless: Lacage ns-3: History and Future March 2012 5 / 27
More requirements Education: Must be easy to use for students Wireless: Must have great validated wireless models Lacage ns-3: History and Future March 2012 5 / 27
More requirements Education: Must be easy to use for students Wireless: Must have great validated wireless models Long term survival: Lacage ns-3: History and Future March 2012 5 / 27
More requirements Education: Must be easy to use for students Wireless: Must have great validated wireless models Long term survival: Maintenance: production-quality code Lacage ns-3: History and Future March 2012 5 / 27
More requirements Education: Must be easy to use for students Wireless: Must have great validated wireless models Long term survival: Maintenance: production-quality code Funding: NSF & INRIA funding finite Lacage ns-3: History and Future March 2012 5 / 27
Long Term Survival Lacage ns-3: History and Future March 2012 6 / 27
Long Term Survival Hard to make enough money to maintain the code: Lacage ns-3: History and Future March 2012 6 / 27
Long Term Survival Hard to make enough money to maintain the code: Small market (network researchers) Lacage ns-3: History and Future March 2012 6 / 27
Long Term Survival Hard to make enough money to maintain the code: Small market (network researchers) Large and complex code Lacage ns-3: History and Future March 2012 6 / 27
Long Term Survival Hard to make enough money to maintain the code: Small market (network researchers) Large and complex code Hard to obtain funding from research agencies: Lacage ns-3: History and Future March 2012 6 / 27
Long Term Survival Hard to make enough money to maintain the code: Small market (network researchers) Large and complex code Hard to obtain funding from research agencies: Funds to use the tool Lacage ns-3: History and Future March 2012 6 / 27
Long Term Survival Hard to make enough money to maintain the code: Small market (network researchers) Large and complex code Hard to obtain funding from research agencies: Funds to use the tool Funds to extend the tool Lacage ns-3: History and Future March 2012 6 / 27
Long Term Survival Hard to make enough money to maintain the code: Small market (network researchers) Large and complex code Hard to obtain funding from research agencies: Funds to use the tool Funds to extend the tool No funds to maintain the tool Lacage ns-3: History and Future March 2012 6 / 27
Open Source Community Lacage ns-3: History and Future March 2012 7 / 27
Open Source Community Hard to create: Lacage ns-3: History and Future March 2012 7 / 27
Open Source Community Hard to create: Licensing is tricky Lacage ns-3: History and Future March 2012 7 / 27
Open Source Community Hard to create: Licensing is tricky Meritocracy Lacage ns-3: History and Future March 2012 7 / 27
Open Source Community Hard to create: Licensing is tricky Meritocracy No discussions behind closed doors Lacage ns-3: History and Future March 2012 7 / 27
Open Source Community Hard to create: Licensing is tricky Meritocracy No discussions behind closed doors Must lose control to see the baby grow Lacage ns-3: History and Future March 2012 7 / 27
Open Source Community Hard to create: Licensing is tricky Meritocracy No discussions behind closed doors Must lose control to see the baby grow Classic management problem: Lacage ns-3: History and Future March 2012 7 / 27
Open Source Community Hard to create: Licensing is tricky Meritocracy No discussions behind closed doors Must lose control to see the baby grow Classic management problem: Spend time to do things yourself Lacage ns-3: History and Future March 2012 7 / 27
Open Source Community Hard to create: Licensing is tricky Meritocracy No discussions behind closed doors Must lose control to see the baby grow Classic management problem: Spend time to do things yourself Spend time to help others do the work Lacage ns-3: History and Future March 2012 7 / 27
Open Source Community Hard to create: Licensing is tricky Meritocracy No discussions behind closed doors Must lose control to see the baby grow Classic management problem: Spend time to do things yourself Spend time to help others do the work It is a hard pill to (make upper management) swallow Lacage ns-3: History and Future March 2012 7 / 27
But the good news is... Lacage ns-3: History and Future March 2012 8 / 27
But the good news is... We (They) all swallowed it. Lacage ns-3: History and Future March 2012 8 / 27
And now, The story of how: Lacage ns-3: History and Future March 2012 9 / 27
And now, The story of how: The Real World pervades everything Lacage ns-3: History and Future March 2012 9 / 27
And now, The story of how: The Real World pervades everything To implement everything 3 or 4 times Aka, Incremental development Lacage ns-3: History and Future March 2012 9 / 27
And now, The story of how: The Real World pervades everything To implement everything 3 or 4 times Aka, Incremental development To not plan too far Lacage ns-3: History and Future March 2012 9 / 27
Outline Introduction Packet Object Framework Conclusion Lacage ns-3: History and Future March 2012 10 / 27
Requirements Lacage ns-3: History and Future March 2012 11 / 27
Requirements Transparent conversion to/from real bytes Lacage ns-3: History and Future March 2012 11 / 27
Requirements Transparent conversion to/from real bytes CPU and memory efficiency Lacage ns-3: History and Future March 2012 11 / 27
Requirements Transparent conversion to/from real bytes CPU and memory efficiency Fragmentation/Reassembly Lacage ns-3: History and Future March 2012 11 / 27
Requirements Transparent conversion to/from real bytes CPU and memory efficiency Fragmentation/Reassembly Simulation-only data Lacage ns-3: History and Future March 2012 11 / 27
Requirements Transparent conversion to/from real bytes CPU and memory efficiency Fragmentation/Reassembly Simulation-only data Pretty printing Lacage ns-3: History and Future March 2012 11 / 27
Requirements Transparent conversion to/from real bytes CPU and memory efficiency Fragmentation/Reassembly Simulation-only data Pretty printing Extensibility Lacage ns-3: History and Future March 2012 11 / 27
Requirements Transparent conversion to/from real bytes CPU and memory efficiency Fragmentation/Reassembly Simulation-only data Pretty printing Extensibility Robust Application Programming Interface (API) Lacage ns-3: History and Future March 2012 11 / 27
Related Work Two approaches Lacage ns-3: History and Future March 2012 12 / 27
Related Work Two approaches Packet is list of headers: GTNetS, OMNeT++, SSFNet MAC IP TCP Payload Lacage ns-3: History and Future March 2012 12 / 27
Related Work Two approaches Packet is list of headers: GTNetS, OMNeT++, SSFNet MAC IP TCP Payload Packet is buffer of bytes: Yans, GloMoSim MAC IP TCP Payload Lacage ns-3: History and Future March 2012 12 / 27
Pros and Cons List Buffer Fragmentation, Reassembly Conversion real bytes Simulation-only data Pretty printing CPU, memory efficiency Lacage ns-3: History and Future March 2012 13 / 27
Pros and Cons List Buffer ns-3 Fragmentation, Reassembly Conversion real bytes Simulation-only data Pretty printing CPU, memory efficiency Lacage ns-3: History and Future March 2012 13 / 27
How did we get there ? About 10 successive versions... Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Started with a simple version in YANS: Headers’ List Tags RefCounting Sep 2005 Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Started with a simple version in YANS: Headers’ List Tags RefCounting Sep 2005 But, hard to integrate the BSD TCP stack Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Real bytes in YANS: Headers’ List Tags RefCounting Jan 2006 Sep 2005 Real Bytes Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Real bytes in YANS: Headers’ List Tags RefCounting Jan 2006 Sep 2005 Real Bytes But, hard to manage reference counting by hand Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Smart Pointers in YANS: Headers’ List Smart Tags Pointers RefCounting Jan 2006 Sep Jun 2005 2006 Real Bytes Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Smart Pointers in YANS: Headers’ List Smart Tags Pointers RefCounting Jan 2006 Sep Jun 2005 2006 Real Bytes But, memory & CPU performance is not good Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Copy On Write in ns-3: Headers’ List Smart Tags Pointers RefCounting Jan Jul 2006 2006 Sep Jun 2005 2006 Real COW Bytes Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Copy On Write in ns-3: Headers’ List Smart Tags Pointers RefCounting Jan Jul 2006 2006 Sep Jun 2005 2006 Real COW Bytes Still, Fast TCP pushes the boundary Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Virtual payload: Headers’ List Smart Virtual Tags Pointers Payload RefCounting Jan Jul 2006 2006 Sep Jun Aug 2005 2006 2006 Real COW Bytes Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Virtual payload: Headers’ List Smart Virtual Tags Pointers Payload RefCounting Jan Jul 2006 2006 Sep Jun Aug 2005 2006 2006 Real COW Bytes Really, debugging is hard Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Packet UIDs: Headers’ List Smart Virtual Tags Pointers Payload RefCounting Jan Jul Sep 2006 2006 2006 Sep Jun Aug 2005 2006 2006 Real Packet COW Bytes UID Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Packet UIDs: Headers’ List Smart Virtual Tags Pointers Payload RefCounting Jan Jul Sep 2006 2006 2006 Sep Jun Aug 2005 2006 2006 Real Packet COW Bytes UID Really, debugging is still hard Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Packet Pretty Printing: Headers’ List Smart Virtual Pretty Tags Pointers Payload Printing RefCounting Jan Jul Sep 2006 2006 2006 Sep Jun Aug May/Jun 2005 2006 2006 2007 Real Packet COW Bytes UID Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Packet Pretty Printing: Headers’ List Smart Virtual Pretty Tags Pointers Payload Printing RefCounting Jan Jul Sep 2006 2006 2006 Sep Jun Aug May/Jun 2005 2006 2006 2007 Real Packet COW Bytes UID But, we do need pointers Lacage ns-3: History and Future March 2012 14 / 27
How did we get there ? Pointers are back: Headers’ List Smart Virtual Pretty Tags Pointers Payload Printing RefCounting Jan Jul Sep Oct 2006 2006 2006 2007 Sep Jun Aug May/Jun 2005 2006 2006 2007 Real Packet COW Ptr<Packet> Bytes UID Lacage ns-3: History and Future March 2012 14 / 27
What I learned the hard way Lacage ns-3: History and Future March 2012 15 / 27
What I learned the hard way The mountain seems impossibly high at first Lacage ns-3: History and Future March 2012 15 / 27
What I learned the hard way The mountain seems impossibly high at first Forget about the top, aim for base camp Lacage ns-3: History and Future March 2012 15 / 27
What I learned the hard way The mountain seems impossibly high at first Forget about the top, aim for base camp The mountain grows with every new user Lacage ns-3: History and Future March 2012 15 / 27
What I learned the hard way The mountain seems impossibly high at first Forget about the top, aim for base camp The mountain grows with every new user Listen to users Lacage ns-3: History and Future March 2012 15 / 27
Outline Introduction Packet Object Framework Conclusion Lacage ns-3: History and Future March 2012 16 / 27
Requirements Lacage ns-3: History and Future March 2012 17 / 27
Requirements Uniform memory management Lacage ns-3: History and Future March 2012 17 / 27
Requirements Uniform memory management Allow simulation configuration Lacage ns-3: History and Future March 2012 17 / 27
Requirements Uniform memory management Allow simulation configuration Solve the object composition problem Lacage ns-3: History and Future March 2012 17 / 27
Requirements Uniform memory management Allow simulation configuration Solve the object composition problem Decouple Trace Sources from Trace Sinks Lacage ns-3: History and Future March 2012 17 / 27
Requirements Uniform memory management Allow simulation configuration Solve the object composition problem Decouple Trace Sources from Trace Sinks Allow simulation trace setup Lacage ns-3: History and Future March 2012 17 / 27
Requirements Uniform memory management Allow simulation configuration Solve the object composition problem Decouple Trace Sources from Trace Sinks Allow simulation trace setup Do not be intrusive to Model developers Lacage ns-3: History and Future March 2012 17 / 27
Fast Forward to 2012 Lacage ns-3: History and Future March 2012 18 / 27
Fast Forward to 2012 Memory management: Ptr<Object> + Dispose Lacage ns-3: History and Future March 2012 18 / 27
Fast Forward to 2012 Memory management: Ptr<Object> + Dispose Configuration: Attributes + ConfigStore Lacage ns-3: History and Future March 2012 18 / 27
Fast Forward to 2012 Memory management: Ptr<Object> + Dispose Configuration: Attributes + ConfigStore Tracing: integrated in Attributes Lacage ns-3: History and Future March 2012 18 / 27
Fast Forward to 2012 Memory management: Ptr<Object> + Dispose Configuration: Attributes + ConfigStore Tracing: integrated in Attributes Configuration, Tracing: optional Lacage ns-3: History and Future March 2012 18 / 27
Fast Forward to 2012 Memory management: Ptr<Object> + Dispose Configuration: Attributes + ConfigStore Tracing: integrated in Attributes Configuration, Tracing: optional Now on par with Omnetpp & Opnet feature-wise Lacage ns-3: History and Future March 2012 18 / 27
A Windy Path It Started with nothing Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path But tom liked the ns-2 default values Default Value Mar 2007 Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path But tom liked the ns-2 default values Default Value Mar 2007 What about memory management, aggregation ? Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Here comes microsoft’s IUnknown! Default Value Apr 2007 Mar 2007 IUnknown Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Here comes microsoft’s IUnknown! Default Value Apr 2007 Mar 2007 IUnknown Scratch that, everyone hates it Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Resolving trace sources: microsoft’s IMoniker Default IMoniker Value Apr 2007 Mar 2007 IUnknown Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Resolving trace sources: microsoft’s IMoniker Default IMoniker Value Apr 2007 Mar 2007 IUnknown Hrm... So, what about memory management ? Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Reference Counting wins Default IMoniker Value Apr 2007 Mar May 2007 2007 Reference IUnknown Counting Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Reference Counting wins Default IMoniker Value Apr 2007 Mar May 2007 2007 Reference IUnknown Counting And Cycles ? Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Dispose to Break the Cycles Default IMoniker Dispose Value Apr 2007 Mar May 2007 2007 Reference IUnknown Counting Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Dispose to Break the Cycles Default IMoniker Dispose Value Apr 2007 Mar May 2007 2007 Reference IUnknown Counting Where is my IUnknown::QueryInterface ? Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Dynamic Aggregation Default IMoniker Dispose Value Apr 2007 Mar May 2007 2007 Reference IUnknown Aggregation Counting Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Dynamic Aggregation Default IMoniker Dispose Value Apr 2007 Mar May 2007 2007 Reference IUnknown Aggregation Counting Ref/Unref by hand still sucks! Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Smart Pointers are back Default IMoniker Dispose Ptr<> Value Apr 2007 Mar May 2007 2007 Reference IUnknown Aggregation Counting Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Smart Pointers are back Default IMoniker Dispose Ptr<> Value Apr 2007 Mar May 2007 2007 Reference IUnknown Aggregation Counting IMoniker is still ugly... Lacage ns-3: History and Future March 2012 19 / 27
A Windy Path Introduce Attributes Default IMoniker Dispose Ptr<> Attributes Value Apr 2007 Mar May Jan-Mar 2007 2007 2008 Reference IUnknown Aggregation Counting Lacage ns-3: History and Future March 2012 19 / 27
With hindsight... Lacage ns-3: History and Future March 2012 20 / 27
With hindsight... I wish: we had looked at Omnetpp & Opnet before Lacage ns-3: History and Future March 2012 20 / 27
With hindsight... I wish: we had looked at Omnetpp & Opnet before The result is still nice thanks to: Willingness to listen to users Lacage ns-3: History and Future March 2012 20 / 27
With hindsight... I wish: we had looked at Omnetpp & Opnet before The result is still nice thanks to: Willingness to listen to users Incremental development Lacage ns-3: History and Future March 2012 20 / 27
No, it is not over Lacage ns-3: History and Future March 2012 21 / 27
No, it is not over Real Code Integration: Linux kernel, Quagga, CCNx, etc. Lacage ns-3: History and Future March 2012 21 / 27
No, it is not over Real Code Integration: Linux kernel, Quagga, CCNx, etc. Contiki Lacage ns-3: History and Future March 2012 21 / 27
No, it is not over Real Code Integration: Linux kernel, Quagga, CCNx, etc. Contiki TinyOS Lacage ns-3: History and Future March 2012 21 / 27
No, it is not over Real Code Integration: Linux kernel, Quagga, CCNx, etc. Contiki TinyOS Brings new challenges: Attributes ? Lacage ns-3: History and Future March 2012 21 / 27
No, it is not over Real Code Integration: Linux kernel, Quagga, CCNx, etc. Contiki TinyOS Brings new challenges: Attributes ? Tracing ? Lacage ns-3: History and Future March 2012 21 / 27
Configuring Attributes Lacage ns-3: History and Future March 2012 22 / 27
Configuring Attributes Linux Kernel: Lacage ns-3: History and Future March 2012 22 / 27
Configuring Attributes Linux Kernel: Bridge /proc/net inside the attribute system Lacage ns-3: History and Future March 2012 22 / 27
Configuring Attributes Linux Kernel: Bridge /proc/net inside the attribute system Difficult to really map one to one Lacage ns-3: History and Future March 2012 22 / 27
Configuring Attributes Linux Kernel: Bridge /proc/net inside the attribute system Difficult to really map one to one Extend Attributes to handle structures, arrays ? Lacage ns-3: History and Future March 2012 22 / 27
Configuring Attributes Linux Kernel: Bridge /proc/net inside the attribute system Difficult to really map one to one Extend Attributes to handle structures, arrays ? Other Applications: Lacage ns-3: History and Future March 2012 22 / 27
Configuring Attributes Linux Kernel: Bridge /proc/net inside the attribute system Difficult to really map one to one Extend Attributes to handle structures, arrays ? Other Applications: I have no idea. Lacage ns-3: History and Future March 2012 22 / 27
Tracing Lacage ns-3: History and Future March 2012 23 / 27
Tracing We do not want to modify the external code: Lacage ns-3: History and Future March 2012 23 / 27
Tracing We do not want to modify the external code: Linux Kernel: Tracepoints, Ftrace, KProbe, etc. Lacage ns-3: History and Future March 2012 23 / 27
Tracing We do not want to modify the external code: Linux Kernel: Tracepoints, Ftrace, KProbe, etc. But no builtin tracing in general Lacage ns-3: History and Future March 2012 23 / 27
Tracing We do not want to modify the external code: Linux Kernel: Tracepoints, Ftrace, KProbe, etc. But no builtin tracing in general Re-implement Kprobe, JProbe, etc. in userspace: Lacage ns-3: History and Future March 2012 23 / 27
Tracing We do not want to modify the external code: Linux Kernel: Tracepoints, Ftrace, KProbe, etc. But no builtin tracing in general Re-implement Kprobe, JProbe, etc. in userspace: Introspection using debug information Lacage ns-3: History and Future March 2012 23 / 27
Tracing We do not want to modify the external code: Linux Kernel: Tracepoints, Ftrace, KProbe, etc. But no builtin tracing in general Re-implement Kprobe, JProbe, etc. in userspace: Introspection using debug information Dynamic patching of assembly code Lacage ns-3: History and Future March 2012 23 / 27
Outline Introduction Packet Object Framework Conclusion Lacage ns-3: History and Future March 2012 24 / 27
Summary Lacage ns-3: History and Future March 2012 25 / 27
Summary What really matters (today): Lacage ns-3: History and Future March 2012 25 / 27
Summary What really matters (today): Alignment with the Real World Lacage ns-3: History and Future March 2012 25 / 27
Summary What really matters (today): Alignment with the Real World An Open Source Community Lacage ns-3: History and Future March 2012 25 / 27
Summary What really matters (today): Alignment with the Real World An Open Source Community Incremental development Lacage ns-3: History and Future March 2012 25 / 27
Summary What really matters (today): Alignment with the Real World An Open Source Community Incremental development No one (but you) knows where ns-3 is headed Lacage ns-3: History and Future March 2012 25 / 27
Thank you ! Questions ? Lacage ns-3: History and Future March 2012 26 / 27
Contact mathieu@cutebugs.net Lacage ns-3: History and Future March 2012 27 / 27

More Related Content

PDF
Tutorial ns 3-tutorial-slides
byVinayagam D
 
PDF
ns-3 Tutorial
bymathieu_lacage
 
PDF
NS3 Tech Talk
byRodrigo Melo
 
PDF
Network Simulation NS3
bybaddi youssef
 
PPTX
~Ns2~
byBhaseerun nisha
 
PDF
Building Topology in NS3
byRahul Hada
 
PDF
1 session installation
byRahul Hada
 
PDF
Ph.D. Defense
bymathieu_lacage
 
Tutorial ns 3-tutorial-slides
byVinayagam D
 
ns-3 Tutorial
bymathieu_lacage
 
NS3 Tech Talk
byRodrigo Melo
 
Network Simulation NS3
bybaddi youssef
 
~Ns2~
byBhaseerun nisha
 
Building Topology in NS3
byRahul Hada
 
1 session installation
byRahul Hada
 
Ph.D. Defense
bymathieu_lacage
 

Viewers also liked

PDF
Inheritance
byRahul Hada
 
PDF
Fundamental of Shell Programming
byRahul Hada
 
PPTX
Ns3
byRehmat Ullah
 
PPT
Chapter 07 php forms handling
byDhani Ahmad
 
PDF
Ns3 implementation wifi
bySalah Amean
 
PPSX
Php and MySQL
byTiji Thomas
 
PDF
NS3 Overview
byRahul Hada
 
PDF
Making web forms using php
bykrishnapriya Tadepalli
 
PDF
Building Complex Topology using NS3
byRahul Hada
 
PPTX
COGNITIVE RADIO
byRahul Sidhu
 
ODP
Form Processing In Php
byHarit Kothari
 
PPTX
Cognitive radio networks
byVatsala Sharma
 
PPT
Php forms
byAnne Lee
 
PPT
Leach & Pegasis
byReenaShekar
 
DOC
Creating a Simple PHP and MySQL-Based Login System
byAzharul Haque Shohan
 
PDF
Memphis php html form processing with php
byJoe Ferguson
 
DOCX
Script login form php
byHanief Rpl
 
PPTX
Php Form
bylotlot
 
PPTX
Cognitive Radio, Introduction and Main Issues
byKuncoro Wastuwibowo
 
PPTX
3 php forms
byhello8421
 
Inheritance
byRahul Hada
 
Fundamental of Shell Programming
byRahul Hada
 
Ns3
byRehmat Ullah
 
Chapter 07 php forms handling
byDhani Ahmad
 
Ns3 implementation wifi
bySalah Amean
 
Php and MySQL
byTiji Thomas
 
NS3 Overview
byRahul Hada
 
Making web forms using php
bykrishnapriya Tadepalli
 
Building Complex Topology using NS3
byRahul Hada
 
COGNITIVE RADIO
byRahul Sidhu
 
Form Processing In Php
byHarit Kothari
 
Cognitive radio networks
byVatsala Sharma
 
Php forms
byAnne Lee
 
Leach & Pegasis
byReenaShekar
 
Creating a Simple PHP and MySQL-Based Login System
byAzharul Haque Shohan
 
Memphis php html form processing with php
byJoe Ferguson
 
Script login form php
byHanief Rpl
 
Php Form
bylotlot
 
Cognitive Radio, Introduction and Main Issues
byKuncoro Wastuwibowo
 
3 php forms
byhello8421
 

Similar to ns-3: History and Future

PDF
How to Become a Hacker?
byremoved_e10bf3fe21ff4e6e6a55bdd2c09fcb15
 
PDF
Web History 101, or How the Future is Unwritten
byBookNet Canada
 
PDF
Umw Software Engineering Guest Lecture 05 Sep2007
byDavid Wood
 
ODP
The Open Source Movement
byHoward Berry
 
DOCX
Timeline History of Internet
byRomana Austria
 
PDF
1 lost layer130123
byARCFIRE ICT
 
PDF
Lost layer talk 2014
byICT PRISTINE
 
PDF
EOLE / OWF 12 - The affero gp lv3. why it exists and who it's for - bradley m...
byParis Open Source Summit
 
DOCX
DESIGN OF A WIRELESS COMMUNICATION SOFTWARE BETWEEN MULTIPLE CLIENTS AND A SI...
byedirin aphunu
 
PDF
"Open Source and the Choice to Cooperate" by Brian Behlendorf @ eLiberatica 2007
byeLiberatica
 
PDF
Consolidate Your Technical Debt With Spark Data Sources -Tools and Techniques...
byDatabricks
 
PPTX
Synchronization
byDavid Evans
 
PDF
Tooling for Change
bySteve Fisher
 
PDF
THE SOCIALIZED INFRASTRUCTURE OF THE INTERNET ON THE COMPUTING LEVEL
byijcsit
 
PDF
THE SOCIALIZED INFRASTRUCTURE OF THE INTERNET ON THE COMPUTING LEVEL
byAIRCC Publishing Corporation
 
PPTX
Class 39: ...and the World Wide Web
byDavid Evans
 
PDF
typical recommending systems
bypashaying
 
PPTX
Internet
byStacy Stevenson
 
ODP
2 b 2-hatta
by真行 八田
 
PDF
Future Interface : What the last 50+ Years of Modern Computing History May Te...
byCA API Management
 
How to Become a Hacker?
byremoved_e10bf3fe21ff4e6e6a55bdd2c09fcb15
 
Web History 101, or How the Future is Unwritten
byBookNet Canada
 
Umw Software Engineering Guest Lecture 05 Sep2007
byDavid Wood
 
The Open Source Movement
byHoward Berry
 
Timeline History of Internet
byRomana Austria
 
1 lost layer130123
byARCFIRE ICT
 
Lost layer talk 2014
byICT PRISTINE
 
EOLE / OWF 12 - The affero gp lv3. why it exists and who it's for - bradley m...
byParis Open Source Summit
 
DESIGN OF A WIRELESS COMMUNICATION SOFTWARE BETWEEN MULTIPLE CLIENTS AND A SI...
byedirin aphunu
 
"Open Source and the Choice to Cooperate" by Brian Behlendorf @ eLiberatica 2007
byeLiberatica
 
Consolidate Your Technical Debt With Spark Data Sources -Tools and Techniques...
byDatabricks
 
Synchronization
byDavid Evans
 
Tooling for Change
bySteve Fisher
 
THE SOCIALIZED INFRASTRUCTURE OF THE INTERNET ON THE COMPUTING LEVEL
byijcsit
 
THE SOCIALIZED INFRASTRUCTURE OF THE INTERNET ON THE COMPUTING LEVEL
byAIRCC Publishing Corporation
 
Class 39: ...and the World Wide Web
byDavid Evans
 
typical recommending systems
bypashaying
 
Internet
byStacy Stevenson
 
2 b 2-hatta
by真行 八田
 
Future Interface : What the last 50+ Years of Modern Computing History May Te...
byCA API Management
 

Recently uploaded

PDF
Data Virtualization in Action: Scaling APIs and Apps with FME
bySafe Software
 
PDF
Security Forum Sessions from Houston 2025 Event
byMark Simos
 
PPTX
Conversational Agents – Building Intelligent Assistants [Virtual Hands-on Wor...
byUiPathCommunity
 
PDF
Unlocking the Power of Salesforce Architecture: Frameworks for Effective Solu...
byvarsha30tiwari
 
PPTX
From Backup to Resilience: How MSPs Are Preparing for 2026
byMSP360
 
PDF
GPUS and How to Program Them by Manya Bansal
byScyllaDB
 
PPT
software-security-intro in information security.ppt
byismaeelsahib032
 
PDF
Day 1 - Cloud Security Strategy and Planning ~ 2nd Sight Lab ~ Cloud Security...
by2nd Sight Lab
 
PDF
The year in review - MarvelClient in 2025
bypanagenda
 
PDF
API-First Architecture in Financial Systems
bycyy111112
 
PPTX
Cloud-and-AI-Platform-FY26-Partner-Playbook.pptx
byiuiuiuiu1
 
PDF
Making Sense of Raster: From Bit Depth to Better Workflows
bySafe Software
 
PDF
Eredità digitale sugli smartphone: cosa resta di noi nei dispositivi mobili
bySpeck&Tech
 
PPTX
Chapter 3 Introduction to number system.pptx
byGetachewAbera9
 
PPTX
Unit-4-ARTIFICIAL NEURAL NETWORKS.pptx ANN ppt Artificial neural network
byssuserd4481a
 
PPTX
AI in Cybersecurity: Digital Defense by Yasir Naveed Riaz
byYasir Naveed Riaz
 
PPTX
Cybercrime in the Digital Age: Risks, Impact & Protection
byYasir Naveed Riaz
 
PPTX
THIS IS CYBER SECURITY NOTES USED IN CLASS ON VARIOUS TOPICS USED IN CYBERSEC...
byMelissaGblinwon
 
PPTX
Cybersecurity Best Practices - Step by Step guidelines
byYasir Naveed Riaz
 
PDF
Session 1 - Solving Semi-Structured Documents with Document Understanding
byDianaGray10
 
Data Virtualization in Action: Scaling APIs and Apps with FME
bySafe Software
 
Security Forum Sessions from Houston 2025 Event
byMark Simos
 
Conversational Agents – Building Intelligent Assistants [Virtual Hands-on Wor...
byUiPathCommunity
 
Unlocking the Power of Salesforce Architecture: Frameworks for Effective Solu...
byvarsha30tiwari
 
From Backup to Resilience: How MSPs Are Preparing for 2026
byMSP360
 
GPUS and How to Program Them by Manya Bansal
byScyllaDB
 
software-security-intro in information security.ppt
byismaeelsahib032
 
Day 1 - Cloud Security Strategy and Planning ~ 2nd Sight Lab ~ Cloud Security...
by2nd Sight Lab
 
The year in review - MarvelClient in 2025
bypanagenda
 
API-First Architecture in Financial Systems
bycyy111112
 
Cloud-and-AI-Platform-FY26-Partner-Playbook.pptx
byiuiuiuiu1
 
Making Sense of Raster: From Bit Depth to Better Workflows
bySafe Software
 
Eredità digitale sugli smartphone: cosa resta di noi nei dispositivi mobili
bySpeck&Tech
 
Chapter 3 Introduction to number system.pptx
byGetachewAbera9
 
Unit-4-ARTIFICIAL NEURAL NETWORKS.pptx ANN ppt Artificial neural network
byssuserd4481a
 
AI in Cybersecurity: Digital Defense by Yasir Naveed Riaz
byYasir Naveed Riaz
 
Cybercrime in the Digital Age: Risks, Impact & Protection
byYasir Naveed Riaz
 
THIS IS CYBER SECURITY NOTES USED IN CLASS ON VARIOUS TOPICS USED IN CYBERSEC...
byMelissaGblinwon
 
Cybersecurity Best Practices - Step by Step guidelines
byYasir Naveed Riaz
 
Session 1 - Solving Semi-Structured Documents with Document Understanding
byDianaGray10
 

ns-3: History and Future

  • 1.
    ns-3: History andFuture Mathieu Lacage March, 24th 2012 Lacage ns-3: History and Future March 2012 1 / 27
  • 2.
    Outline Introduction Packet Object Framework Conclusion Lacage ns-3: History and Future March 2012 2 / 27
  • 3.
    How the projectcame to be Lacage ns-3: History and Future March 2012 3 / 27
  • 4.
    How the projectcame to be Multiple partners: Lacage ns-3: History and Future March 2012 3 / 27
  • 5.
    How the projectcame to be Multiple partners: NSF-funded: UWA, GT, ISI Lacage ns-3: History and Future March 2012 3 / 27
  • 6.
    How the projectcame to be Multiple partners: NSF-funded: UWA, GT, ISI INRIA-funded: planète Lacage ns-3: History and Future March 2012 3 / 27
  • 7.
    How the projectcame to be Multiple partners: NSF-funded: UWA, GT, ISI INRIA-funded: planète Pulling the project in multiple directions: Real Code Long Term Integration Survival ns-3 Wireless Fast TCP Education Emulation Lacage ns-3: History and Future March 2012 3 / 27
  • 8.
    Requirements Lacage ns-3: History and Future March 2012 4 / 27
  • 9.
    Requirements Real-code integration, Emulation: Lacage ns-3: History and Future March 2012 4 / 27
  • 10.
    Requirements Real-code integration, Emulation: Models must not be too abstract (Node, etc.) Lacage ns-3: History and Future March 2012 4 / 27
  • 11.
    Requirements Real-code integration, Emulation: Models must not be too abstract (Node, etc.) Must be transparent to models Lacage ns-3: History and Future March 2012 4 / 27
  • 12.
    Requirements Real-code integration, Emulation: Models must not be too abstract (Node, etc.) Must be transparent to models Fast TCP: Lacage ns-3: History and Future March 2012 4 / 27
  • 13.
    Requirements Real-code integration, Emulation: Models must not be too abstract (Node, etc.) Must be transparent to models Fast TCP: Memory efficiency of many packets in flight Lacage ns-3: History and Future March 2012 4 / 27
  • 14.
    More requirements Lacage ns-3: History and Future March 2012 5 / 27
  • 15.
    More requirements Education: Lacage ns-3: History and Future March 2012 5 / 27
  • 16.
    More requirements Education: Must be easy to use for students Lacage ns-3: History and Future March 2012 5 / 27
  • 17.
    More requirements Education: Must be easy to use for students Wireless: Lacage ns-3: History and Future March 2012 5 / 27
  • 18.
    More requirements Education: Must be easy to use for students Wireless: Must have great validated wireless models Lacage ns-3: History and Future March 2012 5 / 27
  • 19.
    More requirements Education: Must be easy to use for students Wireless: Must have great validated wireless models Long term survival: Lacage ns-3: History and Future March 2012 5 / 27
  • 20.
    More requirements Education: Must be easy to use for students Wireless: Must have great validated wireless models Long term survival: Maintenance: production-quality code Lacage ns-3: History and Future March 2012 5 / 27
  • 21.
    More requirements Education: Must be easy to use for students Wireless: Must have great validated wireless models Long term survival: Maintenance: production-quality code Funding: NSF & INRIA funding finite Lacage ns-3: History and Future March 2012 5 / 27
  • 22.
    Long Term Survival Lacage ns-3: History and Future March 2012 6 / 27
  • 23.
    Long Term Survival Hardto make enough money to maintain the code: Lacage ns-3: History and Future March 2012 6 / 27
  • 24.
    Long Term Survival Hardto make enough money to maintain the code: Small market (network researchers) Lacage ns-3: History and Future March 2012 6 / 27
  • 25.
    Long Term Survival Hardto make enough money to maintain the code: Small market (network researchers) Large and complex code Lacage ns-3: History and Future March 2012 6 / 27
  • 26.
    Long Term Survival Hardto make enough money to maintain the code: Small market (network researchers) Large and complex code Hard to obtain funding from research agencies: Lacage ns-3: History and Future March 2012 6 / 27
  • 27.
    Long Term Survival Hardto make enough money to maintain the code: Small market (network researchers) Large and complex code Hard to obtain funding from research agencies: Funds to use the tool Lacage ns-3: History and Future March 2012 6 / 27
  • 28.
    Long Term Survival Hardto make enough money to maintain the code: Small market (network researchers) Large and complex code Hard to obtain funding from research agencies: Funds to use the tool Funds to extend the tool Lacage ns-3: History and Future March 2012 6 / 27
  • 29.
    Long Term Survival Hardto make enough money to maintain the code: Small market (network researchers) Large and complex code Hard to obtain funding from research agencies: Funds to use the tool Funds to extend the tool No funds to maintain the tool Lacage ns-3: History and Future March 2012 6 / 27
  • 30.
    Open Source Community Lacage ns-3: History and Future March 2012 7 / 27
  • 31.
    Open Source Community Hardto create: Lacage ns-3: History and Future March 2012 7 / 27
  • 32.
    Open Source Community Hardto create: Licensing is tricky Lacage ns-3: History and Future March 2012 7 / 27
  • 33.
    Open Source Community Hardto create: Licensing is tricky Meritocracy Lacage ns-3: History and Future March 2012 7 / 27
  • 34.
    Open Source Community Hardto create: Licensing is tricky Meritocracy No discussions behind closed doors Lacage ns-3: History and Future March 2012 7 / 27
  • 35.
    Open Source Community Hardto create: Licensing is tricky Meritocracy No discussions behind closed doors Must lose control to see the baby grow Lacage ns-3: History and Future March 2012 7 / 27
  • 36.
    Open Source Community Hardto create: Licensing is tricky Meritocracy No discussions behind closed doors Must lose control to see the baby grow Classic management problem: Lacage ns-3: History and Future March 2012 7 / 27
  • 37.
    Open Source Community Hardto create: Licensing is tricky Meritocracy No discussions behind closed doors Must lose control to see the baby grow Classic management problem: Spend time to do things yourself Lacage ns-3: History and Future March 2012 7 / 27
  • 38.
    Open Source Community Hardto create: Licensing is tricky Meritocracy No discussions behind closed doors Must lose control to see the baby grow Classic management problem: Spend time to do things yourself Spend time to help others do the work Lacage ns-3: History and Future March 2012 7 / 27
  • 39.
    Open Source Community Hardto create: Licensing is tricky Meritocracy No discussions behind closed doors Must lose control to see the baby grow Classic management problem: Spend time to do things yourself Spend time to help others do the work It is a hard pill to (make upper management) swallow Lacage ns-3: History and Future March 2012 7 / 27
  • 40.
    But the goodnews is... Lacage ns-3: History and Future March 2012 8 / 27
  • 41.
    But the goodnews is... We (They) all swallowed it. Lacage ns-3: History and Future March 2012 8 / 27
  • 42.
    And now, The storyof how: Lacage ns-3: History and Future March 2012 9 / 27
  • 43.
    And now, The storyof how: The Real World pervades everything Lacage ns-3: History and Future March 2012 9 / 27
  • 44.
    And now, The storyof how: The Real World pervades everything To implement everything 3 or 4 times Aka, Incremental development Lacage ns-3: History and Future March 2012 9 / 27
  • 45.
    And now, The storyof how: The Real World pervades everything To implement everything 3 or 4 times Aka, Incremental development To not plan too far Lacage ns-3: History and Future March 2012 9 / 27
  • 46.
    Outline Introduction Packet Object Framework Conclusion Lacage ns-3: History and Future March 2012 10 / 27
  • 47.
    Requirements Lacage ns-3: History and Future March 2012 11 / 27
  • 48.
    Requirements Transparent conversion to/fromreal bytes Lacage ns-3: History and Future March 2012 11 / 27
  • 49.
    Requirements Transparent conversion to/fromreal bytes CPU and memory efficiency Lacage ns-3: History and Future March 2012 11 / 27
  • 50.
    Requirements Transparent conversion to/fromreal bytes CPU and memory efficiency Fragmentation/Reassembly Lacage ns-3: History and Future March 2012 11 / 27
  • 51.
    Requirements Transparent conversion to/fromreal bytes CPU and memory efficiency Fragmentation/Reassembly Simulation-only data Lacage ns-3: History and Future March 2012 11 / 27
  • 52.
    Requirements Transparent conversion to/fromreal bytes CPU and memory efficiency Fragmentation/Reassembly Simulation-only data Pretty printing Lacage ns-3: History and Future March 2012 11 / 27
  • 53.
    Requirements Transparent conversion to/fromreal bytes CPU and memory efficiency Fragmentation/Reassembly Simulation-only data Pretty printing Extensibility Lacage ns-3: History and Future March 2012 11 / 27
  • 54.
    Requirements Transparent conversion to/fromreal bytes CPU and memory efficiency Fragmentation/Reassembly Simulation-only data Pretty printing Extensibility Robust Application Programming Interface (API) Lacage ns-3: History and Future March 2012 11 / 27
  • 55.
    Related Work Two approaches Lacage ns-3: History and Future March 2012 12 / 27
  • 56.
    Related Work Two approaches Packet is list of headers: GTNetS, OMNeT++, SSFNet MAC IP TCP Payload Lacage ns-3: History and Future March 2012 12 / 27
  • 57.
    Related Work Two approaches Packet is list of headers: GTNetS, OMNeT++, SSFNet MAC IP TCP Payload Packet is buffer of bytes: Yans, GloMoSim MAC IP TCP Payload Lacage ns-3: History and Future March 2012 12 / 27
  • 58.
    Pros and Cons List Buffer Fragmentation, Reassembly Conversion real bytes Simulation-only data Pretty printing CPU, memory efficiency Lacage ns-3: History and Future March 2012 13 / 27
  • 59.
    Pros and Cons List Buffer ns-3 Fragmentation, Reassembly Conversion real bytes Simulation-only data Pretty printing CPU, memory efficiency Lacage ns-3: History and Future March 2012 13 / 27
  • 60.
    How did weget there ? About 10 successive versions... Lacage ns-3: History and Future March 2012 14 / 27
  • 61.
    How did weget there ? Started with a simple version in YANS: Headers’ List Tags RefCounting Sep 2005 Lacage ns-3: History and Future March 2012 14 / 27
  • 62.
    How did weget there ? Started with a simple version in YANS: Headers’ List Tags RefCounting Sep 2005 But, hard to integrate the BSD TCP stack Lacage ns-3: History and Future March 2012 14 / 27
  • 63.
    How did weget there ? Real bytes in YANS: Headers’ List Tags RefCounting Jan 2006 Sep 2005 Real Bytes Lacage ns-3: History and Future March 2012 14 / 27
  • 64.
    How did weget there ? Real bytes in YANS: Headers’ List Tags RefCounting Jan 2006 Sep 2005 Real Bytes But, hard to manage reference counting by hand Lacage ns-3: History and Future March 2012 14 / 27
  • 65.
    How did weget there ? Smart Pointers in YANS: Headers’ List Smart Tags Pointers RefCounting Jan 2006 Sep Jun 2005 2006 Real Bytes Lacage ns-3: History and Future March 2012 14 / 27
  • 66.
    How did weget there ? Smart Pointers in YANS: Headers’ List Smart Tags Pointers RefCounting Jan 2006 Sep Jun 2005 2006 Real Bytes But, memory & CPU performance is not good Lacage ns-3: History and Future March 2012 14 / 27
  • 67.
    How did weget there ? Copy On Write in ns-3: Headers’ List Smart Tags Pointers RefCounting Jan Jul 2006 2006 Sep Jun 2005 2006 Real COW Bytes Lacage ns-3: History and Future March 2012 14 / 27
  • 68.
    How did weget there ? Copy On Write in ns-3: Headers’ List Smart Tags Pointers RefCounting Jan Jul 2006 2006 Sep Jun 2005 2006 Real COW Bytes Still, Fast TCP pushes the boundary Lacage ns-3: History and Future March 2012 14 / 27
  • 69.
    How did weget there ? Virtual payload: Headers’ List Smart Virtual Tags Pointers Payload RefCounting Jan Jul 2006 2006 Sep Jun Aug 2005 2006 2006 Real COW Bytes Lacage ns-3: History and Future March 2012 14 / 27
  • 70.
    How did weget there ? Virtual payload: Headers’ List Smart Virtual Tags Pointers Payload RefCounting Jan Jul 2006 2006 Sep Jun Aug 2005 2006 2006 Real COW Bytes Really, debugging is hard Lacage ns-3: History and Future March 2012 14 / 27
  • 71.
    How did weget there ? Packet UIDs: Headers’ List Smart Virtual Tags Pointers Payload RefCounting Jan Jul Sep 2006 2006 2006 Sep Jun Aug 2005 2006 2006 Real Packet COW Bytes UID Lacage ns-3: History and Future March 2012 14 / 27
  • 72.
    How did weget there ? Packet UIDs: Headers’ List Smart Virtual Tags Pointers Payload RefCounting Jan Jul Sep 2006 2006 2006 Sep Jun Aug 2005 2006 2006 Real Packet COW Bytes UID Really, debugging is still hard Lacage ns-3: History and Future March 2012 14 / 27
  • 73.
    How did weget there ? Packet Pretty Printing: Headers’ List Smart Virtual Pretty Tags Pointers Payload Printing RefCounting Jan Jul Sep 2006 2006 2006 Sep Jun Aug May/Jun 2005 2006 2006 2007 Real Packet COW Bytes UID Lacage ns-3: History and Future March 2012 14 / 27
  • 74.
    How did weget there ? Packet Pretty Printing: Headers’ List Smart Virtual Pretty Tags Pointers Payload Printing RefCounting Jan Jul Sep 2006 2006 2006 Sep Jun Aug May/Jun 2005 2006 2006 2007 Real Packet COW Bytes UID But, we do need pointers Lacage ns-3: History and Future March 2012 14 / 27
  • 75.
    How did weget there ? Pointers are back: Headers’ List Smart Virtual Pretty Tags Pointers Payload Printing RefCounting Jan Jul Sep Oct 2006 2006 2006 2007 Sep Jun Aug May/Jun 2005 2006 2006 2007 Real Packet COW Ptr<Packet> Bytes UID Lacage ns-3: History and Future March 2012 14 / 27
  • 76.
    What I learnedthe hard way Lacage ns-3: History and Future March 2012 15 / 27
  • 77.
    What I learnedthe hard way The mountain seems impossibly high at first Lacage ns-3: History and Future March 2012 15 / 27
  • 78.
    What I learnedthe hard way The mountain seems impossibly high at first Forget about the top, aim for base camp Lacage ns-3: History and Future March 2012 15 / 27
  • 79.
    What I learnedthe hard way The mountain seems impossibly high at first Forget about the top, aim for base camp The mountain grows with every new user Lacage ns-3: History and Future March 2012 15 / 27
  • 80.
    What I learnedthe hard way The mountain seems impossibly high at first Forget about the top, aim for base camp The mountain grows with every new user Listen to users Lacage ns-3: History and Future March 2012 15 / 27
  • 81.
    Outline Introduction Packet Object Framework Conclusion Lacage ns-3: History and Future March 2012 16 / 27
  • 82.
    Requirements Lacage ns-3: History and Future March 2012 17 / 27
  • 83.
    Requirements Uniform memory management Lacage ns-3: History and Future March 2012 17 / 27
  • 84.
    Requirements Uniform memory management Allowsimulation configuration Lacage ns-3: History and Future March 2012 17 / 27
  • 85.
    Requirements Uniform memory management Allowsimulation configuration Solve the object composition problem Lacage ns-3: History and Future March 2012 17 / 27
  • 86.
    Requirements Uniform memory management Allowsimulation configuration Solve the object composition problem Decouple Trace Sources from Trace Sinks Lacage ns-3: History and Future March 2012 17 / 27
  • 87.
    Requirements Uniform memory management Allowsimulation configuration Solve the object composition problem Decouple Trace Sources from Trace Sinks Allow simulation trace setup Lacage ns-3: History and Future March 2012 17 / 27
  • 88.
    Requirements Uniform memory management Allowsimulation configuration Solve the object composition problem Decouple Trace Sources from Trace Sinks Allow simulation trace setup Do not be intrusive to Model developers Lacage ns-3: History and Future March 2012 17 / 27
  • 89.
    Fast Forward to2012 Lacage ns-3: History and Future March 2012 18 / 27
  • 90.
    Fast Forward to2012 Memory management: Ptr<Object> + Dispose Lacage ns-3: History and Future March 2012 18 / 27
  • 91.
    Fast Forward to2012 Memory management: Ptr<Object> + Dispose Configuration: Attributes + ConfigStore Lacage ns-3: History and Future March 2012 18 / 27
  • 92.
    Fast Forward to2012 Memory management: Ptr<Object> + Dispose Configuration: Attributes + ConfigStore Tracing: integrated in Attributes Lacage ns-3: History and Future March 2012 18 / 27
  • 93.
    Fast Forward to2012 Memory management: Ptr<Object> + Dispose Configuration: Attributes + ConfigStore Tracing: integrated in Attributes Configuration, Tracing: optional Lacage ns-3: History and Future March 2012 18 / 27
  • 94.
    Fast Forward to2012 Memory management: Ptr<Object> + Dispose Configuration: Attributes + ConfigStore Tracing: integrated in Attributes Configuration, Tracing: optional Now on par with Omnetpp & Opnet feature-wise Lacage ns-3: History and Future March 2012 18 / 27
  • 95.
    A Windy Path ItStarted with nothing Lacage ns-3: History and Future March 2012 19 / 27
  • 96.
    A Windy Path Buttom liked the ns-2 default values Default Value Mar 2007 Lacage ns-3: History and Future March 2012 19 / 27
  • 97.
    A Windy Path Buttom liked the ns-2 default values Default Value Mar 2007 What about memory management, aggregation ? Lacage ns-3: History and Future March 2012 19 / 27
  • 98.
    A Windy Path Herecomes microsoft’s IUnknown! Default Value Apr 2007 Mar 2007 IUnknown Lacage ns-3: History and Future March 2012 19 / 27
  • 99.
    A Windy Path Herecomes microsoft’s IUnknown! Default Value Apr 2007 Mar 2007 IUnknown Scratch that, everyone hates it Lacage ns-3: History and Future March 2012 19 / 27
  • 100.
    A Windy Path Resolvingtrace sources: microsoft’s IMoniker Default IMoniker Value Apr 2007 Mar 2007 IUnknown Lacage ns-3: History and Future March 2012 19 / 27
  • 101.
    A Windy Path Resolvingtrace sources: microsoft’s IMoniker Default IMoniker Value Apr 2007 Mar 2007 IUnknown Hrm... So, what about memory management ? Lacage ns-3: History and Future March 2012 19 / 27
  • 102.
    A Windy Path ReferenceCounting wins Default IMoniker Value Apr 2007 Mar May 2007 2007 Reference IUnknown Counting Lacage ns-3: History and Future March 2012 19 / 27
  • 103.
    A Windy Path ReferenceCounting wins Default IMoniker Value Apr 2007 Mar May 2007 2007 Reference IUnknown Counting And Cycles ? Lacage ns-3: History and Future March 2012 19 / 27
  • 104.
    A Windy Path Disposeto Break the Cycles Default IMoniker Dispose Value Apr 2007 Mar May 2007 2007 Reference IUnknown Counting Lacage ns-3: History and Future March 2012 19 / 27
  • 105.
    A Windy Path Disposeto Break the Cycles Default IMoniker Dispose Value Apr 2007 Mar May 2007 2007 Reference IUnknown Counting Where is my IUnknown::QueryInterface ? Lacage ns-3: History and Future March 2012 19 / 27
  • 106.
    A Windy Path DynamicAggregation Default IMoniker Dispose Value Apr 2007 Mar May 2007 2007 Reference IUnknown Aggregation Counting Lacage ns-3: History and Future March 2012 19 / 27
  • 107.
    A Windy Path DynamicAggregation Default IMoniker Dispose Value Apr 2007 Mar May 2007 2007 Reference IUnknown Aggregation Counting Ref/Unref by hand still sucks! Lacage ns-3: History and Future March 2012 19 / 27
  • 108.
    A Windy Path SmartPointers are back Default IMoniker Dispose Ptr<> Value Apr 2007 Mar May 2007 2007 Reference IUnknown Aggregation Counting Lacage ns-3: History and Future March 2012 19 / 27
  • 109.
    A Windy Path SmartPointers are back Default IMoniker Dispose Ptr<> Value Apr 2007 Mar May 2007 2007 Reference IUnknown Aggregation Counting IMoniker is still ugly... Lacage ns-3: History and Future March 2012 19 / 27
  • 110.
    A Windy Path IntroduceAttributes Default IMoniker Dispose Ptr<> Attributes Value Apr 2007 Mar May Jan-Mar 2007 2007 2008 Reference IUnknown Aggregation Counting Lacage ns-3: History and Future March 2012 19 / 27
  • 111.
    With hindsight... Lacage ns-3: History and Future March 2012 20 / 27
  • 112.
    With hindsight... I wish: we had looked at Omnetpp & Opnet before Lacage ns-3: History and Future March 2012 20 / 27
  • 113.
    With hindsight... I wish: we had looked at Omnetpp & Opnet before The result is still nice thanks to: Willingness to listen to users Lacage ns-3: History and Future March 2012 20 / 27
  • 114.
    With hindsight... I wish: we had looked at Omnetpp & Opnet before The result is still nice thanks to: Willingness to listen to users Incremental development Lacage ns-3: History and Future March 2012 20 / 27
  • 115.
    No, it isnot over Lacage ns-3: History and Future March 2012 21 / 27
  • 116.
    No, it isnot over Real Code Integration: Linux kernel, Quagga, CCNx, etc. Lacage ns-3: History and Future March 2012 21 / 27
  • 117.
    No, it isnot over Real Code Integration: Linux kernel, Quagga, CCNx, etc. Contiki Lacage ns-3: History and Future March 2012 21 / 27
  • 118.
    No, it isnot over Real Code Integration: Linux kernel, Quagga, CCNx, etc. Contiki TinyOS Lacage ns-3: History and Future March 2012 21 / 27
  • 119.
    No, it isnot over Real Code Integration: Linux kernel, Quagga, CCNx, etc. Contiki TinyOS Brings new challenges: Attributes ? Lacage ns-3: History and Future March 2012 21 / 27
  • 120.
    No, it isnot over Real Code Integration: Linux kernel, Quagga, CCNx, etc. Contiki TinyOS Brings new challenges: Attributes ? Tracing ? Lacage ns-3: History and Future March 2012 21 / 27
  • 121.
    Configuring Attributes Lacage ns-3: History and Future March 2012 22 / 27
  • 122.
    Configuring Attributes Linux Kernel: Lacage ns-3: History and Future March 2012 22 / 27
  • 123.
    Configuring Attributes Linux Kernel: Bridge /proc/net inside the attribute system Lacage ns-3: History and Future March 2012 22 / 27
  • 124.
    Configuring Attributes Linux Kernel: Bridge /proc/net inside the attribute system Difficult to really map one to one Lacage ns-3: History and Future March 2012 22 / 27
  • 125.
    Configuring Attributes Linux Kernel: Bridge /proc/net inside the attribute system Difficult to really map one to one Extend Attributes to handle structures, arrays ? Lacage ns-3: History and Future March 2012 22 / 27
  • 126.
    Configuring Attributes Linux Kernel: Bridge /proc/net inside the attribute system Difficult to really map one to one Extend Attributes to handle structures, arrays ? Other Applications: Lacage ns-3: History and Future March 2012 22 / 27
  • 127.
    Configuring Attributes Linux Kernel: Bridge /proc/net inside the attribute system Difficult to really map one to one Extend Attributes to handle structures, arrays ? Other Applications: I have no idea. Lacage ns-3: History and Future March 2012 22 / 27
  • 128.
    Tracing Lacage ns-3: History and Future March 2012 23 / 27
  • 129.
    Tracing We do notwant to modify the external code: Lacage ns-3: History and Future March 2012 23 / 27
  • 130.
    Tracing We do notwant to modify the external code: Linux Kernel: Tracepoints, Ftrace, KProbe, etc. Lacage ns-3: History and Future March 2012 23 / 27
  • 131.
    Tracing We do notwant to modify the external code: Linux Kernel: Tracepoints, Ftrace, KProbe, etc. But no builtin tracing in general Lacage ns-3: History and Future March 2012 23 / 27
  • 132.
    Tracing We do notwant to modify the external code: Linux Kernel: Tracepoints, Ftrace, KProbe, etc. But no builtin tracing in general Re-implement Kprobe, JProbe, etc. in userspace: Lacage ns-3: History and Future March 2012 23 / 27
  • 133.
    Tracing We do notwant to modify the external code: Linux Kernel: Tracepoints, Ftrace, KProbe, etc. But no builtin tracing in general Re-implement Kprobe, JProbe, etc. in userspace: Introspection using debug information Lacage ns-3: History and Future March 2012 23 / 27
  • 134.
    Tracing We do notwant to modify the external code: Linux Kernel: Tracepoints, Ftrace, KProbe, etc. But no builtin tracing in general Re-implement Kprobe, JProbe, etc. in userspace: Introspection using debug information Dynamic patching of assembly code Lacage ns-3: History and Future March 2012 23 / 27
  • 135.
    Outline Introduction Packet Object Framework Conclusion Lacage ns-3: History and Future March 2012 24 / 27
  • 136.
    Summary Lacage ns-3: History and Future March 2012 25 / 27
  • 137.
    Summary What really matters(today): Lacage ns-3: History and Future March 2012 25 / 27
  • 138.
    Summary What really matters(today): Alignment with the Real World Lacage ns-3: History and Future March 2012 25 / 27
  • 139.
    Summary What really matters(today): Alignment with the Real World An Open Source Community Lacage ns-3: History and Future March 2012 25 / 27
  • 140.
    Summary What really matters(today): Alignment with the Real World An Open Source Community Incremental development Lacage ns-3: History and Future March 2012 25 / 27
  • 141.
    Summary What really matters(today): Alignment with the Real World An Open Source Community Incremental development No one (but you) knows where ns-3 is headed Lacage ns-3: History and Future March 2012 25 / 27
  • 142.
    Thank you ! Questions ? Lacage ns-3: History and Future March 2012 26 / 27
  • 143.
    Contact mathieu@cutebugs.net Lacage ns-3: History and Future March 2012 27 / 27