This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dpacc:minutes20160311 [2016/03/19 23:38] Lingli Deng created |
dpacc:minutes20160311 [2016/03/19 23:55] (current) Lingli Deng [Follow-up actions] |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| ====== Con't Metadata discussion on European call ====== | ====== Con't Metadata discussion on European call ====== | ||
| - | Address: For example, Bar address for PCI device (via IO configuration). Need further examples for non-PCI device (e.g. mem address). | + | - 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? | + | - 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. | + | - 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. | + | - 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. | + | - Mike: where does the requirement for metadata come from? |
| + | - Lingli: refer to gap analysis on openstack for dpacc. | ||
| ====== Update Summary for existing docs ====== | ====== Update Summary for existing docs ====== | ||
| Line 83: | Line 84: | ||
| ====== Follow-up actions ====== | ====== Follow-up actions ====== | ||
| - | - API Guidelines: Revise the current doc to address current comments. | + | - API Guidelines: |
| + | - Revise the current doc to address current comments. | ||
| + | - Need Global Registry for acc ID to be referenced in errcodes | ||
| - Meta Data: | - Meta Data: | ||
| - Contact author of IFA004 for further clarifications on Number of Contexts/Data Format. | - 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. | - Need further input on various element/format specifications for non-PCI accelerators. | ||
| - Initiate C-release planning discussion | - Initiate C-release planning discussion | ||