Академический Документы
Профессиональный Документы
Культура Документы
1. Project Introduction
1. Fun stuff
Kernel
Interface device I
E
Netlink Message Impl. N
G
G
R
R
vport table E
E
Flowtable S
S
S
Packet S
WFP Processing
Callout Hyper-V extensible switch
Driver
MSDN Documentation
of switch 1
1 5
5
I
4. Packet shows up on Egress N
E
G
G
R
path R
E
E
S
2 S
5. Packet sent to destination VM S 3 4
S
NDIS Stack
Typical Ingress Packet Flow with OVS
Kernel 1 4
1
4
“OpenvSwithDevice” device I
E
Netlink Message Impl. N
G
G
R
R
vport table E
E
Flowtable S
2 S
S
Packet S 3
WFP Processing
Callout Hyper-V extensible switch
Driver
• Documentation in datapath-windows/DESIGN
Port management
Tunneling
• IP Helper for ARP resolution & Route lookup
Flowtable/Actions
• Supports all basic actions including set L2/L3
PowerShell cmdlet
• Set the “OVS-Port-Name” of a port to name in OVSDB,
so datapath can map the Hyper-V port to OVS port
Eg. Set-VMNetworkAdapterOVSPortDirect
-VMname Ubuntu-VM
-OVSPortName vif-port-1
Questions?
MSDN Documentation
Netdev-windows
• No native netdev support
• Supports “system” and “internal” ports
• Messy to use Windows APIs like GetAdaptersInfo()
• Netdev commands implemented in kernel datapath
– Get MAC address, MTU, etc
– No support for packet send, receive etc (not needed)
extension I
E
N
• In turn the extension return the packet to the G
G
R
lower driver R
E
E
• Packet return is propagated to the source VM S
2 S
S
• Send complete callback is called on the S 3
NDIS Stack
Typical Ingress Packet Flow