mathieu lacage march, 24th 2012 · lacage a vision of ns-3 march 2012 3 / 27. requirements...
TRANSCRIPT
A personal vision of ns-3
Mathieu Lacage
March, 24th 2012
Lacage A vision of ns-3 March 2012 1 / 27
Outline
Introduction
Packet
Object Framework
Conclusion
Lacage A vision of ns-3 March 2012 2 / 27
How the project came to be
Multiple partners:I NSF-funded: UWA, GT, ISII INRIA-funded: planète
Pulling the project in multiple directions:
Wireless
Long Term
Survival
Fast TCP
Real Code
Integration
EmulationEducation
ns-3
Lacage A vision of ns-3 March 2012 3 / 27
How the project came to beMultiple partners:
I NSF-funded: UWA, GT, ISII INRIA-funded: planète
Pulling the project in multiple directions:
Wireless
Long Term
Survival
Fast TCP
Real Code
Integration
EmulationEducation
ns-3
Lacage A vision of ns-3 March 2012 3 / 27
How the project came to beMultiple partners:
I NSF-funded: UWA, GT, ISI
I INRIA-funded: planètePulling the project in multiple directions:
Wireless
Long Term
Survival
Fast TCP
Real Code
Integration
EmulationEducation
ns-3
Lacage A vision of ns-3 March 2012 3 / 27
How the project came to beMultiple partners:
I NSF-funded: UWA, GT, ISII INRIA-funded: planète
Pulling the project in multiple directions:
Wireless
Long Term
Survival
Fast TCP
Real Code
Integration
EmulationEducation
ns-3
Lacage A vision of ns-3 March 2012 3 / 27
How the project came to beMultiple partners:
I NSF-funded: UWA, GT, ISII INRIA-funded: planète
Pulling the project in multiple directions:
Wireless
Long Term
Survival
Fast TCP
Real Code
Integration
EmulationEducation
ns-3
Lacage A vision of ns-3 March 2012 3 / 27
Requirements
Real-code integration, Emulation:I Models must not be too abstract (Node, etc.)I Must be transparent to models
Fast TCP:I Memory efficiency of many packets in flight
Lacage A vision of ns-3 March 2012 4 / 27
Requirements
Real-code integration, Emulation:
I Models must not be too abstract (Node, etc.)I Must be transparent to models
Fast TCP:I Memory efficiency of many packets in flight
Lacage A vision of ns-3 March 2012 4 / 27
Requirements
Real-code integration, Emulation:I Models must not be too abstract (Node, etc.)
I Must be transparent to modelsFast TCP:
I Memory efficiency of many packets in flight
Lacage A vision of ns-3 March 2012 4 / 27
Requirements
Real-code integration, Emulation:I Models must not be too abstract (Node, etc.)I Must be transparent to models
Fast TCP:I Memory efficiency of many packets in flight
Lacage A vision of ns-3 March 2012 4 / 27
Requirements
Real-code integration, Emulation:I Models must not be too abstract (Node, etc.)I Must be transparent to models
Fast TCP:
I Memory efficiency of many packets in flight
Lacage A vision of ns-3 March 2012 4 / 27
Requirements
Real-code integration, Emulation:I Models must not be too abstract (Node, etc.)I Must be transparent to models
Fast TCP:I Memory efficiency of many packets in flight
Lacage A vision of ns-3 March 2012 4 / 27
More requirements
Education:I Must be easy to use for students
Wireless:I Must have great validated wireless models
Long term survival:I Maintenance: production-quality codeI Funding: NSF & INRIA funding finite
Lacage A vision of ns-3 March 2012 5 / 27
More requirements
Education:
I Must be easy to use for studentsWireless:
I Must have great validated wireless modelsLong term survival:
I Maintenance: production-quality codeI Funding: NSF & INRIA funding finite
Lacage A vision of ns-3 March 2012 5 / 27
More requirements
Education:I Must be easy to use for students
Wireless:I Must have great validated wireless models
Long term survival:I Maintenance: production-quality codeI Funding: NSF & INRIA funding finite
Lacage A vision of ns-3 March 2012 5 / 27
More requirements
Education:I Must be easy to use for students
Wireless:
I Must have great validated wireless modelsLong term survival:
I Maintenance: production-quality codeI Funding: NSF & INRIA funding finite
Lacage A vision of ns-3 March 2012 5 / 27
More requirements
Education:I Must be easy to use for students
Wireless:I Must have great validated wireless models
Long term survival:I Maintenance: production-quality codeI Funding: NSF & INRIA funding finite
Lacage A vision of ns-3 March 2012 5 / 27
More requirements
Education:I Must be easy to use for students
Wireless:I Must have great validated wireless models
Long term survival:
I Maintenance: production-quality codeI Funding: NSF & INRIA funding finite
Lacage A vision of ns-3 March 2012 5 / 27
More requirements
Education:I Must be easy to use for students
Wireless:I Must have great validated wireless models
Long term survival:I Maintenance: production-quality code
I Funding: NSF & INRIA funding finite
Lacage A vision of ns-3 March 2012 5 / 27
More requirements
Education:I Must be easy to use for students
Wireless:I Must have great validated wireless models
Long term survival:I Maintenance: production-quality codeI Funding: NSF & INRIA funding finite
Lacage A vision of ns-3 March 2012 5 / 27
Long Term Survival
Hard to make enough money to maintain the code:I Small market (network researchers)I Large and complex code
Hard to obtain funding from research agencies:I Funds to use the toolI Funds to extend the toolI No funds to maintain the tool
Lacage A vision of ns-3 March 2012 6 / 27
Long Term Survival
Hard to make enough money to maintain the code:
I Small market (network researchers)I Large and complex code
Hard to obtain funding from research agencies:I Funds to use the toolI Funds to extend the toolI No funds to maintain the tool
Lacage A vision of ns-3 March 2012 6 / 27
Long Term Survival
Hard to make enough money to maintain the code:I Small market (network researchers)
I Large and complex codeHard to obtain funding from research agencies:
I Funds to use the toolI Funds to extend the toolI No funds to maintain the tool
Lacage A vision of ns-3 March 2012 6 / 27
Long Term Survival
Hard to make enough money to maintain the code:I Small market (network researchers)I Large and complex code
Hard to obtain funding from research agencies:I Funds to use the toolI Funds to extend the toolI No funds to maintain the tool
Lacage A vision of ns-3 March 2012 6 / 27
Long Term Survival
Hard to make enough money to maintain the code:I Small market (network researchers)I Large and complex code
Hard to obtain funding from research agencies:
I Funds to use the toolI Funds to extend the toolI No funds to maintain the tool
Lacage A vision of ns-3 March 2012 6 / 27
Long Term Survival
Hard to make enough money to maintain the code:I Small market (network researchers)I Large and complex code
Hard to obtain funding from research agencies:I Funds to use the tool
I Funds to extend the toolI No funds to maintain the tool
Lacage A vision of ns-3 March 2012 6 / 27
Long Term Survival
Hard to make enough money to maintain the code:I Small market (network researchers)I Large and complex code
Hard to obtain funding from research agencies:I Funds to use the toolI Funds to extend the tool
I No funds to maintain the tool
Lacage A vision of ns-3 March 2012 6 / 27
Long Term Survival
Hard to make enough money to maintain the code:I Small market (network researchers)I Large and complex code
Hard to obtain funding from research agencies:I Funds to use the toolI Funds to extend the toolI No funds to maintain the tool
Lacage A vision of ns-3 March 2012 6 / 27
Open Source Community
Hard to create:I Licensing is trickyI MeritocracyI No discussions behind closed doorsI Must lose control to see the baby grow
Classic management problem:I Spend time to do things yourselfI Spend time to help others do the work
It is a hard pill to (make upper management) swallow
Lacage A vision of ns-3 March 2012 7 / 27
Open Source Community
Hard to create:
I Licensing is trickyI MeritocracyI No discussions behind closed doorsI Must lose control to see the baby grow
Classic management problem:I Spend time to do things yourselfI Spend time to help others do the work
It is a hard pill to (make upper management) swallow
Lacage A vision of ns-3 March 2012 7 / 27
Open Source Community
Hard to create:I Licensing is tricky
I MeritocracyI No discussions behind closed doorsI Must lose control to see the baby grow
Classic management problem:I Spend time to do things yourselfI Spend time to help others do the work
It is a hard pill to (make upper management) swallow
Lacage A vision of ns-3 March 2012 7 / 27
Open Source Community
Hard to create:I Licensing is trickyI Meritocracy
I No discussions behind closed doorsI Must lose control to see the baby grow
Classic management problem:I Spend time to do things yourselfI Spend time to help others do the work
It is a hard pill to (make upper management) swallow
Lacage A vision of ns-3 March 2012 7 / 27
Open Source Community
Hard to create:I Licensing is trickyI MeritocracyI No discussions behind closed doors
I Must lose control to see the baby growClassic management problem:
I Spend time to do things yourselfI Spend time to help others do the work
It is a hard pill to (make upper management) swallow
Lacage A vision of ns-3 March 2012 7 / 27
Open Source Community
Hard to create:I Licensing is trickyI MeritocracyI No discussions behind closed doorsI Must lose control to see the baby grow
Classic management problem:I Spend time to do things yourselfI Spend time to help others do the work
It is a hard pill to (make upper management) swallow
Lacage A vision of ns-3 March 2012 7 / 27
Open Source Community
Hard to create:I Licensing is trickyI MeritocracyI No discussions behind closed doorsI Must lose control to see the baby grow
Classic management problem:
I Spend time to do things yourselfI Spend time to help others do the work
It is a hard pill to (make upper management) swallow
Lacage A vision of ns-3 March 2012 7 / 27
Open Source Community
Hard to create:I Licensing is trickyI MeritocracyI No discussions behind closed doorsI Must lose control to see the baby grow
Classic management problem:I Spend time to do things yourself
I Spend time to help others do the workIt is a hard pill to (make upper management) swallow
Lacage A vision of ns-3 March 2012 7 / 27
Open Source Community
Hard to create:I Licensing is trickyI MeritocracyI No discussions behind closed doorsI Must lose control to see the baby grow
Classic management problem:I Spend time to do things yourselfI Spend time to help others do the work
It is a hard pill to (make upper management) swallow
Lacage A vision of ns-3 March 2012 7 / 27
Open Source Community
Hard to create:I Licensing is trickyI MeritocracyI No discussions behind closed doorsI Must lose control to see the baby grow
Classic management problem:I Spend time to do things yourselfI Spend time to help others do the work
It is a hard pill to (make upper management) swallow
Lacage A vision of ns-3 March 2012 7 / 27
But the good news is...
We (They) all swallowed it.
Lacage A vision of ns-3 March 2012 8 / 27
But the good news is...
We (They) all swallowed it.
Lacage A vision of ns-3 March 2012 8 / 27
And now,
The story of how:
I The Real World pervades everythingI To implement everything 3 or 4 times
I Aka, Incremental development
I To not plan too far
Lacage A vision of ns-3 March 2012 9 / 27
And now,
The story of how:I The Real World pervades everything
I To implement everything 3 or 4 timesI Aka, Incremental development
I To not plan too far
Lacage A vision of ns-3 March 2012 9 / 27
And now,
The story of how:I The Real World pervades everythingI To implement everything 3 or 4 times
I Aka, Incremental development
I To not plan too far
Lacage A vision of ns-3 March 2012 9 / 27
And now,
The story of how:I The Real World pervades everythingI To implement everything 3 or 4 times
I Aka, Incremental development
I To not plan too far
Lacage A vision of ns-3 March 2012 9 / 27
Outline
Introduction
Packet
Object Framework
Conclusion
Lacage A vision of ns-3 March 2012 10 / 27
Requirements
I Transparent conversion to/from real bytesI CPU and memory efficiencyI Fragmentation/ReassemblyI Simulation-only dataI Pretty printingI ExtensibilityI Robust Application Programming Interface (API)
Lacage A vision of ns-3 March 2012 11 / 27
Requirements
I Transparent conversion to/from real bytes
I CPU and memory efficiencyI Fragmentation/ReassemblyI Simulation-only dataI Pretty printingI ExtensibilityI Robust Application Programming Interface (API)
Lacage A vision of ns-3 March 2012 11 / 27
Requirements
I Transparent conversion to/from real bytesI CPU and memory efficiency
I Fragmentation/ReassemblyI Simulation-only dataI Pretty printingI ExtensibilityI Robust Application Programming Interface (API)
Lacage A vision of ns-3 March 2012 11 / 27
Requirements
I Transparent conversion to/from real bytesI CPU and memory efficiencyI Fragmentation/Reassembly
I Simulation-only dataI Pretty printingI ExtensibilityI Robust Application Programming Interface (API)
Lacage A vision of ns-3 March 2012 11 / 27
Requirements
I Transparent conversion to/from real bytesI CPU and memory efficiencyI Fragmentation/ReassemblyI Simulation-only data
I Pretty printingI ExtensibilityI Robust Application Programming Interface (API)
Lacage A vision of ns-3 March 2012 11 / 27
Requirements
I Transparent conversion to/from real bytesI CPU and memory efficiencyI Fragmentation/ReassemblyI Simulation-only dataI Pretty printing
I ExtensibilityI Robust Application Programming Interface (API)
Lacage A vision of ns-3 March 2012 11 / 27
Requirements
I Transparent conversion to/from real bytesI CPU and memory efficiencyI Fragmentation/ReassemblyI Simulation-only dataI Pretty printingI Extensibility
I Robust Application Programming Interface (API)
Lacage A vision of ns-3 March 2012 11 / 27
Requirements
I Transparent conversion to/from real bytesI CPU and memory efficiencyI Fragmentation/ReassemblyI Simulation-only dataI Pretty printingI ExtensibilityI Robust Application Programming Interface (API)
Lacage A vision of ns-3 March 2012 11 / 27
Related Work
Two approaches
I Packet is list of headers: GTNetS, OMNeT++,SSFNet
TCPIP PayloadMAC
I Packet is buffer of bytes: Yans, GloMoSim
TCPIP PayloadMAC
Lacage A vision of ns-3 March 2012 12 / 27
Related Work
Two approachesI Packet is list of headers: GTNetS, OMNeT++,
SSFNet
TCPIP PayloadMAC
I Packet is buffer of bytes: Yans, GloMoSim
TCPIP PayloadMAC
Lacage A vision of ns-3 March 2012 12 / 27
Related Work
Two approachesI Packet is list of headers: GTNetS, OMNeT++,
SSFNet
TCPIP PayloadMAC
I Packet is buffer of bytes: Yans, GloMoSim
TCPIP PayloadMAC
Lacage A vision of ns-3 March 2012 12 / 27
Pros and Cons
List BufferFragmentation, Reassembly XConversion real bytes XSimulation-only data XPretty printing XCPU, memory efficiency X
Lacage A vision of ns-3 March 2012 13 / 27
Pros and Cons
List Buffer ns-3Fragmentation, Reassembly X XConversion real bytes X XSimulation-only data X XPretty printing X XCPU, memory efficiency X X
Lacage A vision of ns-3 March 2012 13 / 27
How did we get there ?
About 10 successive versions...
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Started with a simple version in YANS:
Headers’ List
Tags
RefCounting
Sep
2005
Lacage A vision of ns-3 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 A vision of ns-3 March 2012 14 / 27
How did we get there ?
Real bytes in YANS:
Headers’ List
Tags
RefCounting
Real
Bytes
Sep
2005
Jan
2006
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Real bytes in YANS:
Headers’ List
Tags
RefCounting
Real
Bytes
Sep
2005
Jan
2006
But, hard to manage reference counting by hand
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Smart Pointers in YANS:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
Bytes
Sep
2005
Jan
2006
Jun
2006
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Smart Pointers in YANS:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
Bytes
Sep
2005
Jan
2006
Jun
2006
But, memory & CPU performance is not good
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Copy On Write in ns-3:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
BytesCOW
Sep
2005
Jan
2006
Jun
2006
Jul
2006
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Copy On Write in ns-3:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
BytesCOW
Sep
2005
Jan
2006
Jun
2006
Jul
2006
Still, Fast TCP pushes the boundary
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Virtual payload:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
BytesCOW
Virtual
Payload
Sep
2005
Jan
2006
Jun
2006
Jul
2006
Aug
2006
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Virtual payload:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
BytesCOW
Virtual
Payload
Sep
2005
Jan
2006
Jun
2006
Jul
2006
Aug
2006
Really, debugging is hard
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Packet UIDs:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
BytesCOW
Virtual
Payload
Packet
UID
Sep
2005
Jan
2006
Jun
2006
Jul
2006
Aug
2006
Sep
2006
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Packet UIDs:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
BytesCOW
Virtual
Payload
Packet
UID
Sep
2005
Jan
2006
Jun
2006
Jul
2006
Aug
2006
Sep
2006
Really, debugging is still hard
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Packet Pretty Printing:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
BytesCOW
Virtual
Payload
Pretty
Printing
Packet
UID
Sep
2005
Jan
2006
Jun
2006
Jul
2006
Aug
2006
Sep
2006
May/Jun
2007
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Packet Pretty Printing:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
BytesCOW
Virtual
Payload
Pretty
Printing
Packet
UID
Sep
2005
Jan
2006
Jun
2006
Jul
2006
Aug
2006
Sep
2006
May/Jun
2007
But, we do need pointers
Lacage A vision of ns-3 March 2012 14 / 27
How did we get there ?
Pointers are back:
Headers’ List
Tags
RefCounting
Smart
Pointers
Real
BytesCOW
Virtual
Payload
Pretty
Printing
Packet
UIDPtr<Packet>
Sep
2005
Jan
2006
Jun
2006
Jul
2006
Aug
2006
Sep
2006
May/Jun
2007
Oct
2007
Lacage A vision of ns-3 March 2012 14 / 27
What I learned the hard way
I The mountain seems impossibly high at firstI Forget about the top, aim for base campI The mountain grows with every new userI Listen to users
Lacage A vision of ns-3 March 2012 15 / 27
What I learned the hard way
I The mountain seems impossibly high at first
I Forget about the top, aim for base campI The mountain grows with every new userI Listen to users
Lacage A vision of ns-3 March 2012 15 / 27
What I learned the hard way
I The mountain seems impossibly high at firstI Forget about the top, aim for base camp
I The mountain grows with every new userI Listen to users
Lacage A vision of ns-3 March 2012 15 / 27
What I learned the hard way
I The mountain seems impossibly high at firstI Forget about the top, aim for base campI The mountain grows with every new user
I Listen to users
Lacage A vision of ns-3 March 2012 15 / 27
What I learned the hard way
I The mountain seems impossibly high at firstI Forget about the top, aim for base campI The mountain grows with every new userI Listen to users
Lacage A vision of ns-3 March 2012 15 / 27
Outline
Introduction
Packet
Object Framework
Conclusion
Lacage A vision of ns-3 March 2012 16 / 27
Requirements
I Uniform memory managementI Allow simulation configurationI Solve the object composition problemI Decouple Trace Sources from Trace SinksI Allow simulation trace setupI Do not be intrusive to Model developers
Lacage A vision of ns-3 March 2012 17 / 27
Requirements
I Uniform memory management
I Allow simulation configurationI Solve the object composition problemI Decouple Trace Sources from Trace SinksI Allow simulation trace setupI Do not be intrusive to Model developers
Lacage A vision of ns-3 March 2012 17 / 27
Requirements
I Uniform memory managementI Allow simulation configuration
I Solve the object composition problemI Decouple Trace Sources from Trace SinksI Allow simulation trace setupI Do not be intrusive to Model developers
Lacage A vision of ns-3 March 2012 17 / 27
Requirements
I Uniform memory managementI Allow simulation configurationI Solve the object composition problem
I Decouple Trace Sources from Trace SinksI Allow simulation trace setupI Do not be intrusive to Model developers
Lacage A vision of ns-3 March 2012 17 / 27
Requirements
I Uniform memory managementI Allow simulation configurationI Solve the object composition problemI Decouple Trace Sources from Trace Sinks
I Allow simulation trace setupI Do not be intrusive to Model developers
Lacage A vision of ns-3 March 2012 17 / 27
Requirements
I Uniform memory managementI Allow simulation configurationI Solve the object composition problemI Decouple Trace Sources from Trace SinksI Allow simulation trace setup
I Do not be intrusive to Model developers
Lacage A vision of ns-3 March 2012 17 / 27
Requirements
I Uniform memory managementI Allow simulation configurationI Solve the object composition problemI Decouple Trace Sources from Trace SinksI Allow simulation trace setupI Do not be intrusive to Model developers
Lacage A vision of ns-3 March 2012 17 / 27
Fast Forward to 2012
I Memory management: Ptr<Object> + DisposeI Configuration: Attributes + ConfigStoreI Tracing: integrated in AttributesI Configuration, Tracing: optional
Now on par with Omnetpp & Opnet feature-wise
Lacage A vision of ns-3 March 2012 18 / 27
Fast Forward to 2012
I Memory management: Ptr<Object> + Dispose
I Configuration: Attributes + ConfigStoreI Tracing: integrated in AttributesI Configuration, Tracing: optional
Now on par with Omnetpp & Opnet feature-wise
Lacage A vision of ns-3 March 2012 18 / 27
Fast Forward to 2012
I Memory management: Ptr<Object> + DisposeI Configuration: Attributes + ConfigStore
I Tracing: integrated in AttributesI Configuration, Tracing: optional
Now on par with Omnetpp & Opnet feature-wise
Lacage A vision of ns-3 March 2012 18 / 27
Fast Forward to 2012
I Memory management: Ptr<Object> + DisposeI Configuration: Attributes + ConfigStoreI Tracing: integrated in Attributes
I Configuration, Tracing: optional
Now on par with Omnetpp & Opnet feature-wise
Lacage A vision of ns-3 March 2012 18 / 27
Fast Forward to 2012
I Memory management: Ptr<Object> + DisposeI Configuration: Attributes + ConfigStoreI Tracing: integrated in AttributesI Configuration, Tracing: optional
Now on par with Omnetpp & Opnet feature-wise
Lacage A vision of ns-3 March 2012 18 / 27
Fast Forward to 2012
I Memory management: Ptr<Object> + DisposeI Configuration: Attributes + ConfigStoreI Tracing: integrated in AttributesI Configuration, Tracing: optional
Now on par with Omnetpp & Opnet feature-wise
Lacage A vision of ns-3 March 2012 18 / 27
A Windy Path
It Started with nothing
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
But tom liked the ns-2 default values
Default
Value
Mar
2007
Lacage A vision of ns-3 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 A vision of ns-3 March 2012 19 / 27
A Windy Path
Here comes microsoft’s IUnknown!
Default
Value
IUnknown
Mar
2007
Apr
2007
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Here comes microsoft’s IUnknown!
Default
Value
IUnknown
Mar
2007
Apr
2007
Scratch that, everyone hates it
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Resolving trace sources: microsoft’s IMoniker
Default
ValueIMoniker
IUnknown
Mar
2007
Apr
2007
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Resolving trace sources: microsoft’s IMoniker
Default
ValueIMoniker
IUnknown
Mar
2007
Apr
2007
Hrm... So, what about memory management ?
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Reference Counting wins
Default
Value
Reference
Counting
IMoniker
IUnknown
Mar
2007
Apr
2007
May
2007
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Reference Counting wins
Default
Value
Reference
Counting
IMoniker
IUnknown
Mar
2007
Apr
2007
May
2007
And Cycles ?
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Dispose to Break the Cycles
Default
ValueDispose
Reference
Counting
IMoniker
IUnknown
Mar
2007
Apr
2007
May
2007
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Dispose to Break the Cycles
Default
ValueDispose
Reference
Counting
IMoniker
IUnknown
Mar
2007
Apr
2007
May
2007
Where is my IUnknown::QueryInterface ?
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Dynamic Aggregation
Default
ValueDispose
Reference
CountingAggregation
IMoniker
IUnknown
Mar
2007
Apr
2007
May
2007
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Dynamic Aggregation
Default
ValueDispose
Reference
CountingAggregation
IMoniker
IUnknown
Mar
2007
Apr
2007
May
2007
Ref/Unref by hand still sucks!
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Smart Pointers are back
Default
ValueDispose
Reference
Counting
Ptr<>
Aggregation
IMoniker
IUnknown
Mar
2007
Apr
2007
May
2007
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Smart Pointers are back
Default
ValueDispose
Reference
Counting
Ptr<>
Aggregation
IMoniker
IUnknown
Mar
2007
Apr
2007
May
2007
IMoniker is still ugly...
Lacage A vision of ns-3 March 2012 19 / 27
A Windy Path
Introduce Attributes
Default
ValueDispose
Reference
Counting
Ptr<>
Aggregation
IMoniker Attributes
IUnknown
Mar
2007
Apr
2007
Jan-Mar
2008
May
2007
Lacage A vision of ns-3 March 2012 19 / 27
With hindsight...
I wish:I we had looked at Omnetpp & Opnet before
The result is still nice thanks to:I Willingness to listen to usersI Incremental development
Lacage A vision of ns-3 March 2012 20 / 27
With hindsight...
I wish:I we had looked at Omnetpp & Opnet before
The result is still nice thanks to:I Willingness to listen to usersI Incremental development
Lacage A vision of ns-3 March 2012 20 / 27
With hindsight...
I wish:I we had looked at Omnetpp & Opnet before
The result is still nice thanks to:I Willingness to listen to users
I Incremental development
Lacage A vision of ns-3 March 2012 20 / 27
With hindsight...
I wish:I we had looked at Omnetpp & Opnet before
The result is still nice thanks to:I Willingness to listen to usersI Incremental development
Lacage A vision of ns-3 March 2012 20 / 27
No, it is not over
Real Code Integration:I Linux kernel, Quagga, CCNx, etc.I ContikiI TinyOS
Brings new challenges:I Attributes ?I Tracing ?
Lacage A vision of ns-3 March 2012 21 / 27
No, it is not over
Real Code Integration:I Linux kernel, Quagga, CCNx, etc.
I ContikiI TinyOS
Brings new challenges:I Attributes ?I Tracing ?
Lacage A vision of ns-3 March 2012 21 / 27
No, it is not over
Real Code Integration:I Linux kernel, Quagga, CCNx, etc.I Contiki
I TinyOSBrings new challenges:
I Attributes ?I Tracing ?
Lacage A vision of ns-3 March 2012 21 / 27
No, it is not over
Real Code Integration:I Linux kernel, Quagga, CCNx, etc.I ContikiI TinyOS
Brings new challenges:I Attributes ?I Tracing ?
Lacage A vision of ns-3 March 2012 21 / 27
No, it is not over
Real Code Integration:I Linux kernel, Quagga, CCNx, etc.I ContikiI TinyOS
Brings new challenges:I Attributes ?
I Tracing ?
Lacage A vision of ns-3 March 2012 21 / 27
No, it is not over
Real Code Integration:I Linux kernel, Quagga, CCNx, etc.I ContikiI TinyOS
Brings new challenges:I Attributes ?I Tracing ?
Lacage A vision of ns-3 March 2012 21 / 27
Configuring Attributes
Linux Kernel:I Bridge /proc/net inside the attribute systemI Difficult to really map one to oneI Extend Attributes to handle structures, arrays ?
Other Applications:I I have no idea.
Lacage A vision of ns-3 March 2012 22 / 27
Configuring Attributes
Linux Kernel:
I Bridge /proc/net inside the attribute systemI Difficult to really map one to oneI Extend Attributes to handle structures, arrays ?
Other Applications:I I have no idea.
Lacage A vision of ns-3 March 2012 22 / 27
Configuring Attributes
Linux Kernel:I Bridge /proc/net inside the attribute system
I Difficult to really map one to oneI Extend Attributes to handle structures, arrays ?
Other Applications:I I have no idea.
Lacage A vision of ns-3 March 2012 22 / 27
Configuring Attributes
Linux Kernel:I Bridge /proc/net inside the attribute systemI Difficult to really map one to one
I Extend Attributes to handle structures, arrays ?Other Applications:
I I have no idea.
Lacage A vision of ns-3 March 2012 22 / 27
Configuring Attributes
Linux Kernel:I Bridge /proc/net inside the attribute systemI Difficult to really map one to oneI Extend Attributes to handle structures, arrays ?
Other Applications:I I have no idea.
Lacage A vision of ns-3 March 2012 22 / 27
Configuring Attributes
Linux Kernel:I Bridge /proc/net inside the attribute systemI Difficult to really map one to oneI Extend Attributes to handle structures, arrays ?
Other Applications:
I I have no idea.
Lacage A vision of ns-3 March 2012 22 / 27
Configuring Attributes
Linux Kernel:I Bridge /proc/net inside the attribute systemI Difficult to really map one to oneI Extend Attributes to handle structures, arrays ?
Other Applications:I I have no idea.
Lacage A vision of ns-3 March 2012 22 / 27
Tracing
We do not want to modify the external code:I Linux Kernel: Tracepoints, Ftrace, KProbe, etc.I But no builtin tracing in general
Re-implement Kprobe, JProbe, etc. in userspace:I Introspection using debug informationI Dynamic patching of assembly code
Lacage A vision of ns-3 March 2012 23 / 27
Tracing
We do not want to modify the external code:
I Linux Kernel: Tracepoints, Ftrace, KProbe, etc.I But no builtin tracing in general
Re-implement Kprobe, JProbe, etc. in userspace:I Introspection using debug informationI Dynamic patching of assembly code
Lacage A vision of ns-3 March 2012 23 / 27
Tracing
We do not want to modify the external code:I Linux Kernel: Tracepoints, Ftrace, KProbe, etc.
I But no builtin tracing in generalRe-implement Kprobe, JProbe, etc. in userspace:
I Introspection using debug informationI Dynamic patching of assembly code
Lacage A vision of ns-3 March 2012 23 / 27
Tracing
We do not want to modify the external code:I Linux Kernel: Tracepoints, Ftrace, KProbe, etc.I But no builtin tracing in general
Re-implement Kprobe, JProbe, etc. in userspace:I Introspection using debug informationI Dynamic patching of assembly code
Lacage A vision of ns-3 March 2012 23 / 27
Tracing
We do not want to modify the external code:I Linux Kernel: Tracepoints, Ftrace, KProbe, etc.I But no builtin tracing in general
Re-implement Kprobe, JProbe, etc. in userspace:
I Introspection using debug informationI Dynamic patching of assembly code
Lacage A vision of ns-3 March 2012 23 / 27
Tracing
We do not want to modify the external code:I Linux Kernel: Tracepoints, Ftrace, KProbe, etc.I But no builtin tracing in general
Re-implement Kprobe, JProbe, etc. in userspace:I Introspection using debug information
I Dynamic patching of assembly code
Lacage A vision of ns-3 March 2012 23 / 27
Tracing
We do not want to modify the external code:I Linux Kernel: Tracepoints, Ftrace, KProbe, etc.I But no builtin tracing in general
Re-implement Kprobe, JProbe, etc. in userspace:I Introspection using debug informationI Dynamic patching of assembly code
Lacage A vision of ns-3 March 2012 23 / 27
Outline
Introduction
Packet
Object Framework
Conclusion
Lacage A vision of ns-3 March 2012 24 / 27
Summary
What really matters (today):I Alignment with the Real WorldI An Open Source CommunityI Incremental developmentI No one (but you) knows where ns-3 is headed
Lacage A vision of ns-3 March 2012 25 / 27
Summary
What really matters (today):
I Alignment with the Real WorldI An Open Source CommunityI Incremental developmentI No one (but you) knows where ns-3 is headed
Lacage A vision of ns-3 March 2012 25 / 27
Summary
What really matters (today):I Alignment with the Real World
I An Open Source CommunityI Incremental developmentI No one (but you) knows where ns-3 is headed
Lacage A vision of ns-3 March 2012 25 / 27
Summary
What really matters (today):I Alignment with the Real WorldI An Open Source Community
I Incremental developmentI No one (but you) knows where ns-3 is headed
Lacage A vision of ns-3 March 2012 25 / 27
Summary
What really matters (today):I Alignment with the Real WorldI An Open Source CommunityI Incremental development
I No one (but you) knows where ns-3 is headed
Lacage A vision of ns-3 March 2012 25 / 27
Summary
What really matters (today):I Alignment with the Real WorldI An Open Source CommunityI Incremental developmentI No one (but you) knows where ns-3 is headed
Lacage A vision of ns-3 March 2012 25 / 27
Thank you !
Questions ?
Lacage A vision of ns-3 March 2012 26 / 27
