diff --git a/.travis/linux-build.sh b/.travis/linux-build.sh index ee615c9ad..19b2ccffc 100755 --- a/.travis/linux-build.sh +++ b/.travis/linux-build.sh @@ -83,7 +83,7 @@ fi if [ "$DPDK" ]; then if [ -z "$DPDK_VER" ]; then - DPDK_VER="17.11" + DPDK_VER="17.11.1" fi install_dpdk $DPDK_VER if [ "$CC" = "clang" ]; then diff --git a/Documentation/faq/releases.rst b/Documentation/faq/releases.rst index 4f805a56c..7c655035a 100644 --- a/Documentation/faq/releases.rst +++ b/Documentation/faq/releases.rst @@ -163,9 +163,9 @@ Q: What DPDK version does each Open vSwitch release work with? 2.4.x 2.0 2.5.x 2.2 2.6.x 16.07.2 - 2.7.x 16.11.4 + 2.7.x 16.11.5 2.8.x 17.05.2 - 2.9.x 17.11 + 2.9.x 17.11.1 ============ ======= Q: I get an error like this when I configure Open vSwitch: diff --git a/Documentation/intro/install/dpdk.rst b/Documentation/intro/install/dpdk.rst index 2cf7cca15..fea48908d 100644 --- a/Documentation/intro/install/dpdk.rst +++ b/Documentation/intro/install/dpdk.rst @@ -40,7 +40,7 @@ Build requirements In addition to the requirements described in :doc:`general`, building Open vSwitch with DPDK will require the following: -- DPDK 17.11 +- DPDK 17.11.1 - A `DPDK supported NIC`_ @@ -69,9 +69,9 @@ Install DPDK #. Download the `DPDK sources`_, extract the file and set ``DPDK_DIR``:: $ cd /usr/src/ - $ wget http://fast.dpdk.org/rel/dpdk-17.11.tar.xz - $ tar xf dpdk-17.11.tar.xz - $ export DPDK_DIR=/usr/src/dpdk-17.11 + $ wget http://fast.dpdk.org/rel/dpdk-17.11.1.tar.xz + $ tar xf dpdk-17.11.1.tar.xz + $ export DPDK_DIR=/usr/src/dpdk-stable-17.11.1 $ cd $DPDK_DIR #. (Optional) Configure DPDK as a shared library diff --git a/Documentation/topics/dpdk/vhost-user.rst b/Documentation/topics/dpdk/vhost-user.rst index 8f203981b..ca8a3289f 100644 --- a/Documentation/topics/dpdk/vhost-user.rst +++ b/Documentation/topics/dpdk/vhost-user.rst @@ -323,9 +323,9 @@ To begin, instantiate a guest as described in :ref:`dpdk-vhost-user` or DPDK sources to VM and build DPDK:: $ cd /root/dpdk/ - $ wget http://fast.dpdk.org/rel/dpdk-17.11.tar.xz - $ tar xf dpdk-17.11.tar.xz - $ export DPDK_DIR=/root/dpdk/dpdk-17.11 + $ wget http://fast.dpdk.org/rel/dpdk-17.11.1.tar.xz + $ tar xf dpdk-17.11.1.tar.xz + $ export DPDK_DIR=/root/dpdk/dpdk-stable-17.11.1 $ export DPDK_TARGET=x86_64-native-linuxapp-gcc $ export DPDK_BUILD=$DPDK_DIR/$DPDK_TARGET $ cd $DPDK_DIR @@ -358,28 +358,6 @@ Finally, start the application:: # TODO -.. important:: - - DPDK v17.11 virtio PMD contains a bug in the vectorized Rx function that - affects testpmd/DPDK guest applications. As such, guest DPDK applications - should use a non-vectorized Rx function. - -The DPDK v17.11 virtio net driver contains a bug that prevents guest DPDK -applications from receiving packets when the vectorized Rx function is used. -This only occurs when guest-bound traffic is live before a DPDK application is -started within the guest, and where two or more forwarding cores are used. As -such, it is not recommended for guests which execute DPDK applications to use -the virtio vectorized Rx function. A simple method of ensuring that a non- -vectorized Rx function is used is to enable mergeable buffers for the guest, -with the following QEMU command line option:: - - mrg_rxbuf=on - -Additional details regarding the virtio driver bug are available on the -`DPDK mailing list`_. - -.. _DPDK mailing list: http://dpdk.org/ml/archives/dev/2017-December/082801.html - .. _dpdk-vhost-user-xml: Sample XML @@ -431,7 +409,7 @@ Sample XML - + @@ -533,4 +511,4 @@ issue can be found on Further information can be found in the `DPDK documentation -`__ +`__