aboutsummaryrefslogtreecommitdiffstats
path: root/build/external/patches
AgeCommit message (Collapse)AuthorFilesLines
2019-03-29Integrate first QUIC protocol implementationNathan Skrzypczak1-0/+57
Currently supports on single stream exposed through standard internal APIs Based on libquicly & picotls by h2o Change-Id: I7bc1ec0e399d1fb02bfd1da91aa7410076d08d14 Signed-off-by: Nathan Skrzypczak <nathan.skrzypczak@gmail.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>
2019-02-02dpdk: bump to dpdk 19.02Damjan Marion9-1231/+0
HQoS requires fixes to work with dpdk 19.02 so code is disabled and pending deprecation unless active maintainer is found. Change-Id: I3569c4287b6dfdd2c29e02375eb53bf01fa6ae84 Signed-off-by: Damjan Marion <damarion@cisco.com>
2018-12-12dpdk: net/bonding: fix buffer corruption in packetsIgor Mikhailov (imichail)1-0/+203
This fix is needed for setup with bonded interfaces. In some scenarios vpp might crash, this change fixes the issue. Change-Id: I0dc66e32b6c89dc3f8d552401833d6785a12c978 Signed-off-by: Igor Mikhailov (imichail) <imichail@cisco.com>
2018-10-26dpdk: fix mlx5 build on SUSEStephen Hemminger1-0/+39
Current mlx5 requires libmnl, and SUSE has a bug which installs the header file in incorrect location. Workaround (from upstream) is to use pkg-config. Change-Id: Iadfd2dc0df211876258c31da028af2e8934483b3 Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
2018-10-26dpdk: ENA PMD patch for failure on port restartMatthew Smith1-0/+359
Patch to fix a bug in the ENA PMD on starting a port that had previously been started and stopped. There was a failure to allocate descriptors on start because they had been allocated during the initial start and not released when the port was stopped. Issue reported/tracked at https://github.com/amzn/amzn-drivers/issues/86 Change-Id: Id9c8d598929f0561788b985011fe5dea8f4a21a5 Signed-off-by: Matthew Smith <mgsmith@netgate.com>
2018-09-25dpdk: add patch to fix 25G AOC cable detectionDamjan Marion1-0/+30
Change-Id: I6b54d4c7767a20b875b5bc05f23a7ac15cb9fbcc Signed-off-by: Damjan Marion <damarion@cisco.com>
2018-09-21add: nasm and ipsec-mb into vpp-ext-deps packagingDamjan Marion7-0/+656
Change-Id: Ie5d85af84ae0d8b15edf5962213ed1b1953bee2f Signed-off-by: Damjan Marion <damarion@cisco.com>