Latest Update DPACC Architecture https docs google comdocumentd1

Latest Update DPACC Architecture https: //docs. google. com/document/d/1 O 4 rt. Ch 1 vb. TOO 5 c. Mwm. Rwf v 3 UJb_b. VWZrq. XQS_-QJAk 10/edit# 10/24/2020

Table of Contents • 1 Introduction • 2 Framework Clarify that SAL is required for DPACC architecture, instead of AC. • 2. 1 Partitioned View • 2. 1. 1 Acceleration Layer for Guest (VM’s) • 2. 1. 2 Acceleration Layer for Host (Hypervisor) • 2. 2 Usage Analysis • 2. 2. 1 Usage: VNF Acceleration types • 2. 2. 2 Usage: VNF Acceleration examples Suggest to refine the figures and text descriptions to clarify the relationship between these two subsections. • 2. 3 Aggregated View • 3 Related Upstream Work Plans

1 Mandate SAL in DPACC Architecture • AC (required? ) SAL (required) • Remove the problematic (required? ) with AC in a section dedicated to the Guest part from the “partitioned view” • Add two sentences to clarify that we need SAL, which includes AC, to be present in the aggregated view. • SAL is the software to hardware abstraction layer, which makes possible additional services which can be controlled by the orchestration layer. SAL can be deployed to either guest or host. SAL is required in all DPACC usages identified in this document.

2 Usage Types and Examples

Todos • Address remain comments • Authors to check the comments • Commenters to confirm remarks and suggestions • Submit to larger group review