1. Figure A: From Openstack Nomad

2. Figure B: From Gap on OpenStack ① ① ④ ④

3. Figure C: From DPACC Architecture SAL: Software Acceleration Layer Provides an abstraction between SW and HW sio-backend: backend of paravirtualized drivers vHost-user: User space based VirtIO interface optional for VM   host access s-API: APIs for utilizing an AC (APIs from the AC) g-drivers: General driver for each device type Implemented in software or the frontend to the hardware (may be different for different acceleration functions) hio: Hardware I/O interface Non-virtualized, accessed only by host SAL AC: Software/Hardware Acceleration Core e.g. DPDK, ODP or other acceleration implementation SRL: Software Routing Layer (Optional layer for the host) Open vSwitch (OVS) or vRouter AML: Acceleration Management Layer To be define for orchestration and spans more than the SAL Acceleration Core (AC) hio sio-backend (optional vHost-user) s-API Acceleration Management Layer Software Acceleration Layer (SAL) Software Routing Layer (SRL) Buffer and memory mgnt, rings/queues, ingress/egress scheduling, tasks, pipeline, … g-drivers SW-crypto or drivers for HW-crypto VM 0VM 2 VM 1 VM 3 VM 4

4. DPACC Management (VIM-NFVI) Figure 3-2 VIM-NFVI acceleration management architecture Acceleration Core (AC) hio sio-backend (optional) s-API Acceleration Management Layer SAL SRL g-drivers SW-crypto or drivers for HW-crypto VM 0 VM 2VM 1 VM 3VM 4 Compute Agent* Acceleration Agent Hypervisor * Compute agent collaborates with Acceleration agent for VM lifecycle managements. VIM Compute Management Function Acceleration Management Function Compute Management Layer Compute Agent* Accelerator CPU/Mem/Disk… guest host device Compute node Control node Questions for discussion 1.EPD is not existent in DPACC arch, sio? 2.⑤ and ⑥ indicate that AML is using userland g-drivers instead of acc drivers in Hypervisor for device access. Current DPACC Arch does not include any components from host kernel. In previous figure, it is not clear whether accelerator driver is in host kernel or not. And it is clear there is a EPD backend driver in hypervisor. 3.need another arrow between Compute Management Function and Acceleration Management Function? For VNF deployment events as described later in Section 5. 4.need to extend sio-backend to expose the host AML to guest? There are such interactions in the previous figure between guest and host. ① ② ③ ④ ⑤ ⑥