1C-202_PANIC A High-Performance Programmable NIC for Multi-tenant Networks-University.PDF

《1C-202_PANIC A High-Performance Programmable NIC for Multi-tenant Networks-University.PDF》由會員分享，可在線閱讀，更多相關《1C-202_PANIC A High-Performance Programmable NIC for Multi-tenant Networks-University.PDF（52頁珍藏版）》請在三個皮匠報告上搜索。

1、PANIC:A HighPANIC:A High-Performance Programmable Performance Programmable NIC for MultiNIC for Multi-tenant Networkstenant NetworksJiaxin Lin1,Kiran Patel,Brent E.Stephens2,Anirudh Sivaraman3and Aditya Akella1123San Jose,CA April 26-28,2022SmartNIC and Multi TenancySmartNICs can help drive increasi

2、ng network line-rates(100Gbps+)by offloading applications or cloud services In the multi-tenant environment,to get benefits from the SmartNIC,servers may want to run multiple offloads on the SmartNIC.SmartNICEmbedded CoresCryptoZipAcceleratorsHashDPUOffloadFirewallTenantsInfrastructureServicesHost2S

3、an Jose,CA April 26-28,2022SmartNIC and Multi TenancySmartNICs can help drive increasing network line-rates(100Gbps+)by offloading applications or cloud services In the multi-tenant environment,to get benefits from the SmartNIC,servers may want to run multiple offloads on the SmartNIC.SmartNICEmbedd

4、ed CoresCryptoZipAcceleratorsHashDPUProblem:None of the current SmartNICs are good at running multiple tenants offloads at the same time.OffloadFirewallTenantsInfrastructureServicesHost2What are the requirements for a SmartNIC in a multi-tenant environment?3San Jose,CA April 26-28,2022Requirements#1

5、 GeneralityGenerality:Different tenants on the host may requires different types of offloads.Both ASIC offload and CPU core should be supported Offload may have below line rate/variable performanceASICOR?4San Jose,CA April 26-28,2022Requirements#2 Flexible ChainingFlexible Chaining:Different tenants

6、 will specify their own chains of offloads.NIC should support sending packets through offloads in any order.IPsecTenant 2:KVS request ChecksumUnzipOn NIC KVS Cache To HostIf protected by IPSec?If compressed?SmartNICTenant 1:Secure RDMA RequestCryptoCongestion ControlRDMATo Host5San Jose,CA April 26-

7、28,2022SmartNICRequirements#3 Isolation#4 PerformanceIsolation:SmartNIC should provide performance isolation between competing tenants.Performance:SmartNIC should provide high throughput for line-rate offloads.SmartNIC should not incur additional latency for low latency offload.Tenant As trafficUnzi

8、pShared OffloadPolicy:WFQ 2:1Tenant Bs traffic6San Jose,CA April 26-28,2022Motivation:Build a programmable NIC that meets all these requirements!7San Jose,CA April 26-28,2022OutlineMotivationImplementation&EvaluationPANICDesign8San Jose,CA April 26-28,2022PANIC Design OverviewPacket BufferCompute Un

9、it 1(Service A)Compute Unit 2(Service B)Compute Unit 3(Service B)Central SchedulerOn-chip MemoryDMAEngineDRAM Controllerport0port1port0port1Switching FabricRMTMAC PHYMAC PHYDDR 4PCIeQSFP28QSFP28port0port1PANIC Components:1.Reconfigurable-Match-Action Pipeline:Parse packets and determine offload chai

10、nChaining:Generality:Isolation:Performance:9San Jose,CA April 26-28,2022PANIC Design OverviewPacket BufferCompute Unit 1(Service A)Compute Unit 2(Service B)Compute Unit 3(Service B)Central SchedulerOn-chip MemoryDMAEngineDRAM Controllerport0port1port0port1Switching FabricRMTMAC PHYMAC PHYDDR 4PCIeQS

11、FP28QSFP28port0port1PANIC Components:1.Reconfigurable-Match-Action Pipeline:Parse packets and determine offload chain2.Central Scheduler:enforce isolation policies and schedule packetsChaining:Generality:Isolation:Performance:9San Jose,CA April 26-28,2022PANIC Design OverviewPacket BufferCompute Uni

12、t 1(Service A)Compute Unit 2(Service B)Compute Unit 3(Service B)Central SchedulerOn-chip MemoryDMAEngineDRAM Controllerport0port1port0port1Switching FabricRMTMAC PHYMAC PHYDDR 4PCIeQSFP28QSFP28port0port1PANIC Components:1.Reconfigurable-Match-Action Pipeline:Parse packets and determine offload chain

13、2.Central Scheduler:enforce isolation policies and schedule packets3.Independent Compute Unit:Support hardware accelerator or CPU coreChaining:Generality:Isolation:Performance:9San Jose,CA April 26-28,2022PANIC Design OverviewPacket BufferCompute Unit 1(Service A)Compute Unit 2(Service B)Compute Uni

14、t 3(Service B)Central SchedulerOn-chip MemoryDMAEngineDRAM Controllerport0port1port0port1Switching FabricRMTMAC PHYMAC PHYDDR 4PCIeQSFP28QSFP28port0port1PANIC Components:1.Reconfigurable-Match-Action Pipeline:Parse packets and determine offload chain2.Central Scheduler:enforce isolation policies and

15、 schedule packets3.Independent Compute Unit:Support hardware accelerator or CPU core4.High-throughput Switching Fabric:Interconnects different hardware resources.Chaining:Generality:Isolation:Performance:9San Jose,CA April 26-28,2022PANIC Design OverviewPacket BufferCompute Unit 1(Service A)Compute

16、Unit 2(Service B)Compute Unit 3(Service B)Central SchedulerOn-chip MemoryDMAEngineDRAM Controllerport0port1port0port1Switching FabricRMTMAC PHYMAC PHYDDR 4PCIeQSFP28QSFP28port0port1PANIC Components:1.Reconfigurable-Match-Action Pipeline:Parse packets and determine offload chain2.Central Scheduler:en

17、force isolation policies and schedule packets3.Independent Compute Unit:Support hardware accelerator or CPU core4.High-throughput Switching Fabric:Interconnects different hardware resources.Chaining:Generality:Isolation:Performance:9San Jose,CA April 26-28,2022PANIC Design OverviewPacket BufferCompu

18、te Unit 1(Service A)Compute Unit 2(Service B)Compute Unit 3(Service B)Central SchedulerOn-chip MemoryDMAEngineDRAM Controllerport0port1port0port1Switching FabricRMTMAC PHYMAC PHYDDR 4PCIeQSFP28QSFP28port0port1PANIC Components:1.Reconfigurable-Match-Action Pipeline:Parse packets and determine offload

19、 chain2.Central Scheduler:enforce isolation policies and schedule packets3.Independent Compute Unit:Support hardware accelerator or CPU core4.High-throughput Switching Fabric:Interconnects different hardware resources.Chaining:Generality:Isolation:Performance:9San Jose,CA April 26-28,2022Life-Cycle

20、of a Packet in PANICPacket BufferCU 1CU 2CU 3On-chip MemoryDMAEngineSwitching FabricRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerService AService BService AScheduler10San Jose,CA April 26-28,2022Life-Cycle of a Packet in PANICPacket BufferCU 1CU 2CU 3On-chip MemoryDMAEngineSwi

21、tching FabricRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerService AService BService AService ANetwork PacketService BTo HostIf from WAN?If compressed?Scheduler10San Jose,CA April 26-28,2022Life-Cycle of a Packet in PANICPacket BufferCU 1CU 2CU 3On-chip MemoryDMAEngineSwitching

22、 FabricRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerService AService BService AService ANetwork PacketService BTo HostIf from WAN?If compressed?Scheduler10San Jose,CA April 26-28,2022Life-Cycle of a Packet in PANICPacket BufferCU 1CU 2CU 3On-chip MemoryDMAEngineSwitching Fabri

23、cRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerPK_LENBUF_ADDRCHAIN:A-B0163236CHAIN_LEN:2variableService AService BService AService ANetwork PacketService BTo HostIf from WAN?If compressed?Scheduler10San Jose,CA April 26-28,2022Life-Cycle of a Packet in PANICPacket BufferCU 1CU

24、2CU 3On-chip MemoryDMAEngineSwitching FabricRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerPK_LENBUF_ADDRCHAIN:A-B0163236CHAIN_LEN:2variableService AService BService AService ANetwork PacketService BTo HostIf from WAN?If compressed?Scheduler10San Jose,CA April 26-28,2022Life-Cyc

25、le of a Packet in PANICPacket BufferCU 1CU 2CU 3On-chip MemoryDMAEngineSwitching FabricRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerPK_LENBUF_ADDRCHAIN:A-B0163236CHAIN_LEN:2variableService AService BService AService ANetwork PacketService BTo HostIf from WAN?If compressed?Sche

26、duler10San Jose,CA April 26-28,2022Life-Cycle of a Packet in PANICPacket BufferCU 1CU 2CU 3On-chip MemoryDMAEngineSwitching FabricRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerPK_LENBUF_ADDRCHAIN:A-B0163236CHAIN_LEN:2variableService AService BService AService ANetwork PacketSer

27、vice BTo HostIf from WAN?If compressed?Scheduler10San Jose,CA April 26-28,2022Life-Cycle of a Packet in PANICPacket BufferCU 1CU 2CU 3On-chip MemoryDMAEngineSwitching FabricRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerPK_LENBUF_ADDRCHAIN:A-B0163236CHAIN_LEN:2variableService AS

28、ervice BService AService ANetwork PacketService BTo HostIf from WAN?If compressed?Scheduler10San Jose,CA April 26-28,2022Life-Cycle of a Packet in PANICPacket BufferCU 1CU 2CU 3On-chip MemoryDMAEngineSwitching FabricRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerPK_LENBUF_ADDRCH

29、AIN:A-B0163236CHAIN_LEN:2variableService AService BService AService ANetwork PacketService BTo HostIf from WAN?If compressed?Scheduler10San Jose,CA April 26-28,2022Life-Cycle of a Packet in PANICPacket BufferCU 1CU 2CU 3On-chip MemoryDMAEngineSwitching FabricRMTMAC PHYMAC PHYport0port1HW Priority Qu

30、eue(PIFO)ArrayCreditManagerPK_LENBUF_ADDRCHAIN:A-B0163236CHAIN_LEN:2variableService AService BService AService ANetwork PacketService BTo HostIf from WAN?If compressed?Scheduler10San Jose,CA April 26-28,2022Life-Cycle of a Packet in PANICPacket BufferCU 1CU 2CU 3On-chip MemoryDMAEngineSwitching Fabr

31、icRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerPK_LENBUF_ADDRCHAIN:A-B0163236CHAIN_LEN:2variableService AService BService AService ANetwork PacketService BTo HostIf from WAN?If compressed?Scheduler10San Jose,CA April 26-28,2022Life-Cycle of a Packet in PANICPacket BufferCU 1CU

32、 2CU 3On-chip MemoryDMAEngineSwitching FabricRMTMAC PHYMAC PHYport0port1HW Priority Queue(PIFO)ArrayCreditManagerPK_LENBUF_ADDRCHAIN:A-B0163236CHAIN_LEN:2variableService AService BService AService ANetwork PacketService BTo HostIf from WAN?If compressed?Scheduler10San Jose,CA April 26-28,2022RMT Pip

33、eline&Switching FabricRMT pipeline:Users program the match action tables in RMT.The service chain for each tenants traffic.The isolation policy and priority number for each tenants traffic.Action stage,RMT generates a PANIC descriptor for every packet11PK_LENBUF_ADDRCHAIN:A-BCHAIN_LEN:2SCHE_METADATA

34、:Switching Fabric:Providing offload chaining for an arbitrary chain.Each interconnect port should send and receive at full line-rate(100Gbps)San Jose,CA April 26-28,2022PANIC Scheduler:Goal#1:Achieve high-performance chainingGoal#2:Load-balance packets across parallel compute units in a serviceGoal#

35、3:Performance isolation across tenantsGoal#4:Buffer isolation across tenants12San Jose,CA April 26-28,2022Problem:Chaining and Load Balancing Pull-based schedulingSchedulerCU1CU2pullpullService AService BEvery hop goes back to scheduler;cannot achieve high performance chaining!Achieve Load balancing

36、!Goal#1:Achieve high-performance chainingGoal#2:Load-balance packets across parallel compute units in a service.a13San Jose,CA April 26-28,2022Problem:Chaining and Load Balancing Pull-based scheduling Push-based schedulingSchedulerCU1CU2pullpullService AService BEvery hop goes back to scheduler;cann

37、ot achieve high performance chaining!Achieve Load balancing!SchedulerCU1CU2CU3Service AService BService BpushpushGoal#1:Achieve high-performance chainingGoal#2:Load-balance packets across parallel compute units in a service.a13San Jose,CA April 26-28,2022Problem:Chaining and Load Balancing Pull-base

38、d scheduling Push-based schedulingSchedulerCU1CU2pullpullService AService BEvery hop goes back to scheduler;cannot achieve high performance chaining!Lead to load imbalance!Achieve Load balancing!Low latency chaining!SchedulerCU1CU2CU3Service AService BService BpushpushLead to packet dropping!Goal#1:

39、Achieve high-performance chainingGoal#2:Load-balance packets across parallel compute units in a service.a13San Jose,CA April 26-28,2022Problem:Chaining and Load Balancing Pull-based scheduling Push-based schedulingSchedulerCU1CU2pullpullService AService BEvery hop goes back to scheduler;cannot achie

40、ve high performance chaining!Lead to load imbalance!Achieve Load balancing!Low latency chaining!SchedulerCU1CU2CU3Service AService BService BpushpushLead to packet dropping!Goal#1:Achieve high-performance chainingGoal#2:Load-balance packets across parallel compute units in a service.aSolution:Hybrid

41、 push-pull scheduling13San Jose,CA April 26-28,2022PANIC Scheduler:Hybrid Push Pull Scheduling Hybrid Push Pull scheduling:CU can either pull packet from the scheduler or accept the pushed packet from other units.According to CUs load,switches between push pull scheduling.During Low Load:the packet

42、is pushed to all the units in a chain.SchedulerCU1CU21.pull2.pushAchieve High Performance Chaining!14San Jose,CA April 26-28,2022PANIC Scheduler:Hybrid Push Pull Scheduling Hybrid Push Pull scheduling:CU can either pull packet from the scheduler or accept the pushed packet from other units.According

43、 to CUs load,switches between push pull scheduling.During Low Load:the packet is pushed to all the units in a chain.During High Load:the packet is sent back to the scheduler,until it can be pulled by an idle CU.SchedulerCU1CU21.pull2.pushSchedulerCU1CU21.pull3.pull2.send backAchieve Load balancing!A

44、chieve High Performance Chaining!14San Jose,CA April 26-28,2022PANIC Scheduler:Hybrid Push Pull Scheduling Hybrid Push Pull scheduling:CU can either pull packet from the scheduler or accept the pushed packet from other units.According to CUs load,switches between push pull scheduling.During Low Load

45、:the packet is pushed to all the units in a chain.During High Load:the packet is sent back to the scheduler,until it can be pulled by an idle CU.Detour Routing:In push scheduling,if the downstream is busy due to a burst.SchedulerCU1CU21.pull2.pushSchedulerCU1CU21.pull2.pushBUSY!3.detourSchedulerCU1C

46、U21.pull3.pull2.send backAchieve Load balancing!Achieve High Performance Chaining!Avoid Packet Dropping14San Jose,CA April 26-28,2022PANIC Scheduler:Performance IsolationGoal#3:Priority scheduling and performance isolationPacket BufferPIFO Array PIFO array for performance Isolation:PIFO(PUSH IN,FIRS

47、T OUT Queue)runs like the hardware priority queue.One service has one logic PIFO queue.ABCScheduler15San Jose,CA April 26-28,2022PANIC Scheduler:Performance IsolationGoal#3:Priority scheduling and performance isolationPacket BufferPIFO Array PIFO array for performance Isolation:PIFO(PUSH IN,FIRST OU

48、T Queue)runs like the hardware priority queue.One service has one logic PIFO queue.Packet descriptors is sorted according to the packet rank in per-service PIFO.Service ATenant 1:10Gbps Priority=0(Highest)Tenant 2:90Gbps Priority=10(Low)Service BService CABCIsolation Policy:Strict PriorityScheduler1

49、5San Jose,CA April 26-28,2022PANIC Scheduler:Performance IsolationGoal#3:Priority scheduling and performance isolationPacket BufferPIFO Array PIFO array for performance Isolation:PIFO(PUSH IN,FIRST OUT Queue)runs like the hardware priority queue.One service has one logic PIFO queue.Packet descriptor

50、s is sorted according to the packet rank in per-service PIFO.Service ATenant 1:10Gbps Priority=0(Highest)Tenant 2:90Gbps Priority=10(Low)Service BService CABCIsolation Policy:Strict PrioritySchedulerPK_LENBUF_ADDRCHAIN:A-BCHAIN_LEN:2SCHE_METADATA:15San Jose,CA April 26-28,2022PANIC Scheduler:Perform

51、ance IsolationGoal#3:Priority scheduling and performance isolationPacket BufferPIFO Array PIFO array for performance Isolation:PIFO(PUSH IN,FIRST OUT Queue)runs like the hardware priority queue.One service has one logic PIFO queue.Packet descriptors is sorted according to the packet rank in per-serv

52、ice PIFO.Service ATenant 1:10Gbps Priority=0(Highest)Tenant 2:90Gbps Priority=10(Low)Service BService CABCIsolation Policy:Strict PrioritySchedulerPK_LENBUF_ADDRCHAIN:A-BCHAIN_LEN:2SCHE_METADATA:15San Jose,CA April 26-28,2022PANIC Scheduler:Performance IsolationGoal#3:Priority scheduling and perform

53、ance isolationPacket BufferPIFO Array PIFO array for performance Isolation:PIFO(PUSH IN,FIRST OUT Queue)runs like the hardware priority queue.One service has one logic PIFO queue.Packet descriptors is sorted according to the packet rank in per-service PIFO.Support different isolation policy (WFQ,LST

54、F,Rate Limiting)Service ATenant 1:10Gbps Priority=0(Highest)Tenant 2:90Gbps Priority=10(Low)Service BService CABCIsolation Policy:Strict PrioritySchedulerPK_LENBUF_ADDRCHAIN:A-BCHAIN_LEN:2SCHE_METADATA:15San Jose,CA April 26-28,2022PANIC Scheduler:Prioritized Dropping16Service ATenant 1:10Gbps Prior

55、ity=0(Highest)Tenant 2:90Gbps Priority=10(Low)Service BService CIsolation Policy:Strict PriorityPacket BufferPIFO ArrayABCSchedulerGoal#4:Ensure buffer isolation across tenants Nave dropping method:drop the newest income packet when the buffer is full:No Isolation!San Jose,CA April 26-28,2022PANIC S

56、cheduler:Prioritized Dropping16Service ATenant 1:10Gbps Priority=0(Highest)Tenant 2:90Gbps Priority=10(Low)Service BService CIsolation Policy:Strict PriorityPacket BufferPIFO ArrayABCSchedulerGoal#4:Ensure buffer isolation across tenants Nave dropping method:drop the newest income packet when the bu

57、ffer is full:No Isolation!Prioritized Dropping:drop the lowest rank packet when the buffer is almost full.Extend PIFOs interface to allow it to support PUSH IN,FIRST OUT,REMOVE LAST Isolation!PANIC can ensure the high priority packet enters buffer and receive service.San Jose,CA April 26-28,2022PANI

58、C Scheduler:Prioritized Dropping16Service ATenant 1:10Gbps Priority=0(Highest)Tenant 2:90Gbps Priority=10(Low)Service BService CIsolation Policy:Strict PriorityPacket BufferPIFO ArrayABCSchedulerGoal#4:Ensure buffer isolation across tenants Nave dropping method:drop the newest income packet when the

59、 buffer is full:No Isolation!Prioritized Dropping:drop the lowest rank packet when the buffer is almost full.Extend PIFOs interface to allow it to support PUSH IN,FIRST OUT,REMOVE LAST Isolation!PANIC can ensure the high priority packet enters buffer and receive service.San Jose,CA April 26-28,2022P

60、ANIC Scheduler:Prioritized Dropping16Service ATenant 1:10Gbps Priority=0(Highest)Tenant 2:90Gbps Priority=10(Low)Service BService CIsolation Policy:Strict PriorityPacket BufferPIFO ArrayABCSchedulerGoal#4:Ensure buffer isolation across tenants Nave dropping method:drop the newest income packet when

61、the buffer is full:No Isolation!Prioritized Dropping:drop the lowest rank packet when the buffer is almost full.Extend PIFOs interface to allow it to support PUSH IN,FIRST OUT,REMOVE LAST Isolation!PANIC can ensure the high priority packet enters buffer and receive service.San Jose,CA April 26-28,20

62、22PANIC Scheduler:Prioritized Dropping16Service ATenant 1:10Gbps Priority=0(Highest)Tenant 2:90Gbps Priority=10(Low)Service BService CIsolation Policy:Strict PriorityPacket BufferPIFO ArrayABCSchedulerGoal#4:Ensure buffer isolation across tenants Nave dropping method:drop the newest income packet wh

63、en the buffer is full:No Isolation!Prioritized Dropping:drop the lowest rank packet when the buffer is almost full.Extend PIFOs interface to allow it to support PUSH IN,FIRST OUT,REMOVE LAST Isolation!PANIC can ensure the high priority packet enters buffer and receive service.San Jose,CA April 26-28

64、,2022PANIC Implementation 100G FPGA prototype in ADM-PCIE-9V3 accelerator 6K lines of Verilog code Prototype Components:o A lightweight RMT pipelineo 8*8 full connected crossbar(512 bit width 250MHz)o Dual-port central scheduler(512 bit width 250MHz)PIFO block 125MHzo Compute Units AES-256-CTR encry

65、ption unit(24Gbps 250Mhz)SHA-3-512 hash unit(32Gbps 150Mhz)An RISC-V core unit(5-stage pipeline 250MHz)18https:/bitbucket.org/uw-madison-networking-research/panic_osdi20_artifact/San Jose,CA April 26-28,2022PANIC Evaluation19Setup:The sender server generate network traffic using different traffic pa

66、ttern.2 SHA engines and 2 AES engines are attached.Isolation Policy:weighted fair queuing.Traffic Group 1SHA(S1,S2)Traffic Group 2AES(A1,A2)32Gbps*224Gbps*2Traffic Group 3Weight=1Weight=2PANICBackground020406080100135791113151719212325Throughput(Gbps)Time(s)G1G2BGTOTAL30GbpsG1G2BG70Gbps0Gbps50Gbps50

67、Gbps0Gbps30Gbps30Gbps40GbpsTraffic PatternPhase 1Phase 2Phase 3San Jose,CA April 26-28,2022PANIC Evaluation19Setup:The sender server generate network traffic using different traffic pattern.2 SHA engines and 2 AES engines are attached.Isolation Policy:weighted fair queuing.Traffic Group 1SHA(S1,S2)T

68、raffic Group 2AES(A1,A2)32Gbps*224Gbps*2Traffic Group 3Weight=1Weight=2PANICBackground020406080100135791113151719212325Throughput(Gbps)Time(s)G1G2BGTOTAL30GbpsG1G2BG70Gbps0Gbps50Gbps50Gbps0Gbps30Gbps30Gbps40GbpsTraffic PatternPhase 1Phase 2Phase 3San Jose,CA April 26-28,2022PANIC Evaluation19Setup:T

69、he sender server generate network traffic using different traffic pattern.2 SHA engines and 2 AES engines are attached.Isolation Policy:weighted fair queuing.Traffic Group 1SHA(S1,S2)Traffic Group 2AES(A1,A2)32Gbps*224Gbps*2Traffic Group 3Weight=1Weight=2PANICBackground020406080100135791113151719212

70、325Throughput(Gbps)Time(s)G1G2BGTOTAL30GbpsG1G2BG70Gbps0Gbps50Gbps50Gbps0Gbps30Gbps30Gbps40GbpsTraffic PatternPhase 1Phase 2Phase 3San Jose,CA April 26-28,2022Conclusion PANIC is a full line-rate programmable NIC design that overcomes current NICs limitation in multi-tenant environments.20San Jose,CA April 26-28,2022Thank you for listening!Questions?21