1 <!-- http://microformats.org/wiki/hcalendar -->
3 <span class="organiser">Pavel Emelyanov</span>
5 Why network namespace sucks and how to make it suck faster
8 <a class="url" href="http://linuxplumbersconf.org/ocw/proposals/81">Linux Plumbers Conference</a>,
9 <span class="location">Portland, OR</span>,
10 <abbr class="dtstart" title="20090923">Wednesday, September 23, 2009 from 10:30 – 10:55am</span>
11 <div class="description">
12 The talk outlines various ways of establishing a networking
13 communication between a network namespace (a container)
14 and the outer world, compares their performance and features.
16 Each namespace implements its own isolated network stack.
17 Network packets comes to a network stack from network device.
18 Five different device types that can be used as a packets
19 sources for containers are demonstrated. Their properties
20 (mostly performance and maintainability) and features are
23 In addition, one more device type is described — the one that is currently
24 only implemented in the OpenVZ containers. Its pros and cons,
25 and ways it can be implemented in the mainline kernel are discussed.