This shows you the differences between two versions of the page.
Last revision Both sides next revision | |||
dpacc:minutes20160311 [2016/03/19 23:38] Lingli Deng created |
dpacc:minutes20160311 [2016/03/19 23:54] Lingli Deng [Con't Metadata discussion on European call] |
||
---|---|---|---|
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 ====== |