Building a Fast, Virtualized Building a Fast, Virtualized Data - - PowerPoint PPT Presentation

building a fast virtualized building a fast virtualized
SMART_READER_LITE
LIVE PREVIEW

Building a Fast, Virtualized Building a Fast, Virtualized Data - - PowerPoint PPT Presentation

Building a Fast, Virtualized Building a Fast, Virtualized Data Plane with Data Plane with Programmable Hardware Programmable Hardware Bilal Anwer Nick Feamster 1 Network Virtualization Network Virtualization Network virtualization enables


slide-1
SLIDE 1

1

Building a Fast, Virtualized Data Plane with Programmable Hardware Building a Fast, Virtualized Data Plane with Programmable Hardware

Bilal Anwer Nick Feamster

slide-2
SLIDE 2

2

Network Virtualization Network Virtualization

  • Network virtualization enables many virtual networks to

share the same physical network resources.

  • Many possible applications:

– Hosting of multiple service provider networks – Experimentation – Running new protocols side‐by‐side with old ones

slide-3
SLIDE 3

3

Fixed Network Infrastructure Fixed Network Infrastructure

slide-4
SLIDE 4

4

Shared Infrastructure Shared Infrastructure

Networks have illusion of dedicated hardware.

slide-5
SLIDE 5

5

Network Virtualization: Requirements Network Virtualization: Requirements

  • Scalability

– Support large number of networks (implies sharing)

  • Performance

– Support real traffic at line rate

  • Flexibility

– Support custom network services

  • Isolation

– Protection of networks from each other

slide-6
SLIDE 6

6

Goal: Fast, Virtualized Data Plane Goal: Fast, Virtualized Data Plane

  • Strawman approach: Software

– Provides flexibility – …but poor performance and often inadequate isolation

  • Our approach

– Control plane in software – Data plane in hardware – Share hardware elements among virtual networks where possible

slide-7
SLIDE 7

7

Virtualized Data Plane Virtualized Data Plane

Router-1 Router-6 Router-2 Router-5 Router-3 Router-7 Router-8

Source Sink

2 Ethernet links 16 Ethernet links

Router-4

Virtual router

Router-4

slide-8
SLIDE 8

8

Hardware‐Based Virtualization Hardware‐Based Virtualization

  • Forwarding in hardware

– faster than software – provides better isolation

  • Sharing physical substrate amortizes cost

– Unused hardware resources are already paid for

  • Key challenge: Design must take advantage of both

hardware and software

– Requires interface between hardware and software – Requires identifying elements that can be shared among many virtual networks

slide-9
SLIDE 9

9

Design Overview

  • Control plane

– two contexts – virtual environments in OpenVZ

  • Interface to

NetFPGA based

  • n NetFPGA

reference router

slide-10
SLIDE 10

10

Talk Outline Talk Outline

  • Implementation

– Virtualization at Layer 2 – Fast forwarding – Resource guarantees per virtual network

  • Preliminary Results

– Performance & Efficiency

  • Conclusion and Future Work
slide-11
SLIDE 11

11

Virtualization at Layer 2 Virtualization at Layer 2

VRouter-1 VRouter-6 VRouter-2 VRouter-5 VRouter-3 VRouter-7 VRouter-8 Source VRouter-4 VMAC- VE Table Sink

00:11:22:33:44:55

00:11:22:33:44:55

0x1

00:11:22:33:44:55l

slide-12
SLIDE 12

12

Layer‐2 Virtualization: VMAC‐VE Table Layer‐2 Virtualization: VMAC‐VE Table

  • VMAC‐VE Table

– provides virtualization at Layer 2 – maintains states for virtual Ethernet interfaces of each virtual environment

  • Current implementation

– Max. of four Ethernet interfaces per virtual router (currently limited by on‐chip memory) – Max. of eight virtual routers working in parallel

  • Hence, 32 Table Entries
slide-13
SLIDE 13

13

Mapping the Virtual Forwarding Tables Mapping the Virtual Forwarding Tables

VMAC in packet determines the virtual network (and, hence, which CAMs to use)

slide-14
SLIDE 14

14

Resource Guarantees Resource Guarantees

  • CPU Isolation

– Provided by using PCI‐based NetFPGA card

  • Bandwidth Isolation

– Virtual networks are not affected by each other if they abide by their allocated bandwidth – What if user steps beyond allocated limited?

  • Currently, no enforcement (limitation)
  • Limit could be enforced at either ingress or egress
slide-15
SLIDE 15

15

Evaluation Evaluation

  • What forwarding rates does the architecture achieve?
  • How do these rates compare to the forwarding rate of

the base hardware?

  • How will the architecture scale with future hardware

trends?

slide-16
SLIDE 16

16

Experimental Setup Experimental Setup

slide-17
SLIDE 17

17

Forwarding Performance: Rates Forwarding Performance: Rates

Forwarding Rate (‘000 pps) Packet Size (bytes)

Packet forwarding rates are at least as good as Linux kernel. (~2.5x for small packets)

slide-18
SLIDE 18

18

Forwarding Performance: Overhead Forwarding Performance: Overhead

Forwarding Rate (‘000 pps) Packet Size (bytes)

Performance of up to eight virtual routers is equivalent to base router.

slide-19
SLIDE 19

19

Efficiency Efficiency

  • Base router:

45% of logic, 53% of BRAM, 8.6M gates

  • 8 Virtual Routers:

69% of logic, 87% of BRAM, 14.1M gates

Virtual Routers

Cards will support more virtual routers as Xilinx technology improves.

slide-20
SLIDE 20

20

Future Work Future Work

  • Adding support for forwarding tables on SRAM.
  • Providing bandwidth isolation when users exceed

allocated bandwidth.

  • Providing an interface to each user for performance

statistics, etc.

slide-21
SLIDE 21

21

Summary: Fast, Virtualized Data Plane Summary: Fast, Virtualized Data Plane

  • Scalable

– Design is scalable (Off‐chip FIB will allow more virtual data planes.)

  • Fast

– Current implementation has the same performance as base hardware

  • Flexible

– Support for custom control and data planes

  • Provides Isolation

– Virtual networks don’t interfere with each other if traffic within limits

slide-22
SLIDE 22

22

Conclusion Conclusion

  • Resource sharing in routers using programmable

hardware is possible

  • Hardware resource sharing provides improved isolation

and packet forwarding rates than software based solution

  • Current implementation achieves isolation and

forwarding performance of native hardware without any

  • verhead
slide-23
SLIDE 23

23

slide-24
SLIDE 24

24

Extra Extra

slide-25
SLIDE 25

25

Extra Extra

slide-26
SLIDE 26

26

Extra Extra

slide-27
SLIDE 27

27

Performance Overhead Performance Overhead

  • Tested with 1,2,3,4,5,6,7,8 virtualized data‐planes

working in parallel and for 64‐byte sized packets

  • The forwarding rate was same for all eight virtualized

data configuration

  • All eight configuration showed forwarding rate equal to

base router forwarding rate for 64‐byte sized packets