1. Figure 3-2 VIM-NFVI acceleration management architecture
Questions for discussion
EPD is not existent in DPACC arch, sio? YES.
⑤ and ⑥ indicate that AML is using userland g-drivers via s-API instead of acc drivers in Hypervisor for device access.
Need further review and feedback.
need another arrow between Compute Management Function and Acceleration Management Function?
For VNF deployment events as described later in Section 5. YES.
need to extend sio-backend to expose the host AML to guest?
There are such interactions in the previous figure between guest and host.
No. VNF is agnostic to VIM orchestration and management.
Such interactions is not meant for configuration rather than orchestration and is not related to AML.
guest
VM 0
VM 1
VM 2
VM 3
VM 4
DPACC Management (VIM-NFVI)
sio-backend (optional)
Acceleration Agent
Compute Agent*
SRL ⑤
Acceleration Management Layer
Compute Management Layer ①
Acceleration Core (AC)
s-API
Compute Management
Function
VIM
Compute Management
Function
host
Compute Management
Function ④
g-drivers
SW-crypto or drivers for HW-crypto
Acceleration
Management
Function ②
hio
SAL
Hypervisor
Control node ⑥ ③
device
Accelerator
CPU/Mem/Disk…
* Compute agent collaborates with Acceleration agent for VM lifecycle managements.
Compute node

2. Figure A: From Openstack Nomad

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

4. 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
VM 0
VM 1
VM 2
VM 3
VM 4
sio-backend (optional vHost-user)
Software Routing Layer (SRL)
Acceleration Core (AC)
s-API
Software Acceleration Layer (SAL)
Acceleration Management Layer
Buffer and memory mgnt, rings/queues, ingress/egress scheduling, tasks, pipeline, …
g-drivers
SW-crypto or drivers for HW-crypto
hio