Agenda
Attendants
Lingli, Howard, Keith, Arei, Denis, Rajesh, Paul, Varun, Arun, Mike, Michele
Address: For example, Bar address for PCI device (via IO configuration). Need further examples for non-PCI device (e.g. mem address).
Vendor-ID/Device-ID: Mike: 0 for SW acc is a common practice. Varun: not sure it is the case. Lingli: Do we differentiate software accelerators from different vendors?
Varun: no sure why VNF needs to be aware of the vendor-id or device-id of the HW acc? Lingli: this is for mgmt agent rather than VNF applications.
Lingli: call for input for non-PCI device and SW acc.
Mike: where does the requirement for metadata come from?
Lingli: refer to gap analysis on openstack for dpacc.
Update Summary for existing docs
Existing docs
No update to dpacc arch and openstack gap or use-case
A slide for addresing a comment on use-case doc is provided
* Reference to the arch doc is used to clarify that the PDCP usecase in the usecase doc is aligned with the dpacc arch.
* Lingli will put the comment and reply online and contact original commenter Ola for further confirmation if the concern is addressed or not.
New Doc for API Guidelines
_accmodel_
Common operations: set & modify
Operations of "set" and "modify"
Agreement: The verb ‘set’ is preferred because it better aligns with ‘get’. Eliminates the verb ‘modify’, minimizing the number of verbs.
Return Values (err codes)
Response Arguments
It is proposed to Removed cb_arg_len field.
Keith: Instead of having per API callback with different arg list, can we use a single callback function for all API specified by application during device open, with fixed number of arguments?
Keith: the argv list for the callback could be fixed or variable using varargs if that makes it simpler. The varargs code does add some complexity, but maybe it is worth using.
Denis/Rajesh: Study the possibility and get back
NOMAD Southbound API
Follow-up actions
-
Revise the current doc to address current comments.
Need Global Registry for acc ID to be referenced in errcodes
Meta Data:
Contact author of IFA004 for further clarifications on Number of Contexts/Data Format.
Need further input on various element/format specifications for non-PCI accelerators.
Initiate C-release planning discussion