summary |
shortlog |
log |
commit | commitdiff |
review |
tree
raw |
patch |
inline | side by side (from parent 1:
4e95c60)
Change-Id: Ib1175c8eb256136e9d4b5342043c2014d99631e6
Signed-off-by: Tibor Frank <tifrank@cisco.com>
List of known issues in |csit-release| for DPDK performance tests:
List of known issues in |csit-release| for DPDK performance tests:
-+----+------------------------------------------+----------------------------------------------------------------------------------------------------------+
-| # | JiraID | Issue Description |
-+====+==========================================+==========================================================================================================+
++----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
+| # | JiraID | Issue Description |
++====+=========================================+===========================================================================================================+
| 1 | `CSIT-1761 | Denverton systems in FD.io CSIT lab (2n-dnv and 3n-dnv) reports dpdk compilation error very often. |
| | <https://jira.fd.io/browse/CSIT-1761>`_ | |
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
| 1 | `CSIT-1761 | Denverton systems in FD.io CSIT lab (2n-dnv and 3n-dnv) reports dpdk compilation error very often. |
| | <https://jira.fd.io/browse/CSIT-1761>`_ | |
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
Known Issues
------------
Known Issues
------------
-List of known issues in |csit-release| for VPP performance tests: TODO: check
+List of known issues in |csit-release| for VPP performance tests:
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
| # | JiraID | Issue Description |
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
| # | JiraID | Issue Description |
| | <https://jira.fd.io/browse/VPP-1675>`_ | Reason: chained buffers are not supported. |
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
| 6 | `VPP-1934 | [i40e] Interfaces are not brought up from carrier-down. |
| | <https://jira.fd.io/browse/VPP-1675>`_ | Reason: chained buffers are not supported. |
+----+-----------------------------------------+-----------------------------------------------------------------------------------------------------------+
| 6 | `VPP-1934 | [i40e] Interfaces are not brought up from carrier-down. |
-| | <https://jira.fd.io/browse/VPP-1934 >`_ | In case of i40e -based interface (e.g Intel x700 series NIC) is bound to kernel driver (i40e) and is in |
+| | <https://jira.fd.io/browse/VPP-1934>`_ | In case of i40e -based interface (e.g Intel x700 series NIC) is bound to kernel driver (i40e) and is in |
| | | state "no-carrier" (<NO-CARRIER,BROADCAST,MULTICAST,UP>) because previously it was disabled via |
| | | "I40E_AQ_PHY_LINK_ENABLED" call, then VPP during initialization of AVF interface is not re-enabling |
| | | interface link via i40e driver to up. |
| | | state "no-carrier" (<NO-CARRIER,BROADCAST,MULTICAST,UP>) because previously it was disabled via |
| | | "I40E_AQ_PHY_LINK_ENABLED" call, then VPP during initialization of AVF interface is not re-enabling |
| | | interface link via i40e driver to up. |