Enhanced Memory Management

Transcription

1 Enhanced Memory Management DPDK Smmit - San Jose 2017 #DPDKSmmit

2 Challenges The world is changing Adapt to varying application reqirements Performance, Secrity, Footprint, Robstness? Native, Containers, VMs, Unikernels? x86, ARM, PowerPC,? Linx, BSD, Windows,? Abstract complexities of the environment from applications Different environments with variable ways to allocate/attach to memory Same valid for other resorces sch as network interfaces, HW accelerators etc. 2

3 Crrent Limitations Static hgepage memory allocation at DPDK initialization time Dynamic allocation is not possible Memory initialization takes a long time (collecting, mapping, zeroing) DPDK relies on physical memory information (not always available) Physically contigos segments (allocation failre if no physically contigos mem) PMDs rely on physical memory for DMA No virtally contigos memory spport No spport for memory mapped files, shared memory segments, ivshmem, ramfs etc. 3

4 DPDK Today Memory Initialization DPDK grabs all reqired hgepages and fills p its heap dring initialization Everything is mapped with R/W permissions in all processes Un-initialized memory DPDK memory R/W #1 #2 #3 4

5 DPDK Today Mlti-process Seqence 1) Primary Proc #1 and Proc #2 started 2) Proc #1 inits memory, Proc #2 is waiting 3) Primary Proc #1 releases lock, Proc #2 attaches to DPDK memory 4) Both processes start allocating memory at the same time (lock contention) No Isolation! No Memory Protection! No fine grain control of object placement! Primary #1 DPDK memory Zzzz #2 DPDK socket 0 (except NUMA and page sizes) memory allocated/sed by #1 memory allocated/sed by #2 5

6 Enhanced Memory Manager Framework Applications DPDK External Memory Plgin md_reserve md_attach md_attach Enhanced Memory Manager Framework Memory Domain Memory allocator manager Hgepages Heap/mmap Shared Mem IVSHM 6

7 Proposal Both DPDK and the enhanced memory manager are sed by applications Maintain backward compatibility Applications cold directly se memdomain APIs to get reqired memory on demand Extend DPDK to spport external memory manager plgins DPDK wold be a ser of memory domain Enhanced memory manager is a framework spport many types of memory allocators, sch as hgepages, mmap/heap, shared memory, or inter-vm shared memory 7

8 Named Memory Partitions - Featre DPDK/Apps are attaching to named partitions pools (memdomains) Mltiple processes can attach to partitions with distinct access rights es/threads can attach to named partitions on-demand memdomain MainMem LocalMem{{ type = nma exclsive cpalias = all app_fg policy = static on-demand size { hge_ = 128MB hge_4k 4GB } hge_2m = 256MB no_zero = tre } } DPDK memory MainMem LocalMem[2] LocalMem[1] Un-initialized memory Localmem[3] R/W R/O #1 #2 #3 8

9 Named Memory Partitions - Seqence 1) Primary Proc #1 and Proc #2 started 2) Primary Proc #1 inits MainMem partition 3) Proc #2 awakes, attaches to MainMem 4) Proc #1 and #2 attaches to LocalMem (allocates/maps partition) no zero on req. 5) Both processes start allocating memory within their own partition (no contention) Access Control! Placement Control! Isolation! Memory Protection! Primary #1 4K/2M DPDK Socket 0 LocalMem[1] DPDK SocketId 1<<8 Zzzz #2 LocalMem[2] DPDK SocketId 2<<8 DPDK memory memory allocated/sed by #1 memzones allocated/sed by #2 9

10 Named Memory Partitions - Possibilities Flexible environment specific configration Adapt to different architectres, e.g. no page-size hard-coding in application Adopting configration to reqired policy, e.g. Performance, Secrity, Footprint Performance tning accelerated by pblishing different configrations Access control Memory classification External resorce manager managing the resorces of applications rnning in containers or VMs Creating fast/medim/slow partitions on x86 (zero TLB miss, 2M hge, 4K) Physically contigos memory partition only for DMA 10

11 Named Memory Partitions - Possibilities Virtal address space control: Short pointer spport by reqesting specific virtal address range On demand static or dynamic virtal address assignment Transparent NUMA awareness Scale p/down Allocate/Free resorces on-demand as processes start/stop Spport of different types of shared memory techniqes Each process reqests local memory partition which is created based on the location of that instance Named partition for Inter-container or Inter-VM shared memory (global namespace) etc. 11

12 Previos Work DPDK Smmit 2014 DPDK Userspace

13 Qestions? Laszlo Vadkerti Jiangtao Zhang

14 THANK YOU!