summaryrefslogtreecommitdiffstats
path: root/build/external/patches/dpdk_19.02
AgeCommit message (Collapse)AuthorFilesLines
2019-10-31build: remove obsolete dpdk patchesDamjan Marion2-132/+0
Type: refactor Change-Id: I2bad8d4e7b9d7868c949856d0bbabeccb6825273 Signed-off-by: Damjan Marion <damarion@cisco.com>
2019-04-02dpdk 19.02: fixed speed capability error issueChenmin Sun1-0/+101
Device speed capability should be specified based on different phy types instead of a fixed value, this patch fix the issue. Change-Id: Ia76231aefbcb0fe8370867b6e86a0d3bb9e169a0 Signed-off-by: Chenmin Sun <chenmin.sun@intel.com>
2019-03-22dpdk: add ENIC PMD patch to untag default vlanHyong Youb Kim1-0/+31
The ingress vlan rewrite mode affects the vlan header of ingress packet. The enic driver currently uses the 'passthrough' mode, which leaves the vlan header intact. As all packets in UCS network are tagged, this default mode leads to tagged ingress packets in the following cases where VPP expects untagged packets. 1. Trunk-mode vNIC on UCS standalone server. A remote device sends an untagged packet to the server. This packet is ultimately tagged with vlan 0 as it reaches the driver, and VPP sees an ingress packet tagged with vlan 0. 2. Access-mode vNIC on UCS blade or standalone server. A remote device sends a packet on the vNIC's default vlan (e.g. 200) to the server. This tag is untouched, and VPP sees an ingress packet tagged with the default vlan (e.g. 200). In both cases, VPP expects to see untagged packets. To work around the issue, VPP currently enables vlan stripping on VIC interfaces, which breaks vlan sub-interface features. To avoid the current workaround, use the "untag default vlan" rewrite mode. With this mode, the VIC adapter removes the vlan header if it matches the default vlan. In the cases described above, VPP would see untagged packets. Packets tagged with non-default vlan (e.g. non-0 for case 1 and non-200 for case 2) are received with their tags intact, so VPP sees tagged packets as expected. The driver currently has no programmatic way to change the rewrite mode after rte_eal_init. So use this patch to change the mode for the time being. Change-Id: Iff6408275363ed52d6016e7516d745214d6b30d4 Signed-off-by: Hyong Youb Kim <hyonkim@cisco.com>