HI Kevin, The setup is: 1. Add one virtio_user port to OVS with 3 queues ovs-vsctl add-port br0 virtio_user0 -- set Interface virtio_user0 type=dpdk options:dpdk-devargs=net_virtio_user0,iface=tap0,path=/dev/vhost-net,queues=3
2. Inject traffic 3. traffic should eb received at virtio_user port ? Regards, Suneetha -----Original Message----- From: Kevin Traynor <[email protected]> Sent: 21 September 2021 17:43 To: Kalahasthi, Suneetha <[email protected]>; [email protected] Cc: David Marchand <[email protected]> Subject: Re: [ovs-dev] [PATCH] dpdk: Use DPDK 20.11.3 release On 21/09/2021 11:42, Kevin Traynor wrote: > On 21/09/2021 08:08, Suneetha Kalahasthi wrote: >> Modify ci linux build script to use the latest DPDK stable release 20.11.3. >> Modify Documentation to use the latest DPDK stable release 20.11.3. >> Update NEWS file to reflect the latest DPDK stable release 20.11.3. >> FAQ is updated to reflect the latest DPDK for each OVS branch. >> > > David has reported a crash for virtio_user devices with 20.11.3 [1]. I > ran a quick test of adding a virtio_user port to OVS and there was no > crash, but maybe it was not a full test or I was lucky. > After talking to David, I reproduced with: ovs-vsctl add-port br0 virtio_user0 -- set Interface virtio_user0 type=dpdk options:dpdk-devargs=net_virtio_user0,iface=tap0,path=/dev/vhost-net,queues=3 You'd need to check if there are fixes impacting OVS in 20.11.3 that make it better to take now and document this known issue. Otherwise, probably better to wait until 20.11.4 with the fix for this. > Can you check if it is ok to use 20.11.3 with this known issue? > > [1] > http://inbox.dpdk.org/dev/CAJFAV8yjvEvk-YQgwBb=ZAWCrn_P2NDzcugC2W-O+7J > [email protected]/ > >> Signed-off-by: Suneetha Kalahasthi <[email protected]> >> --- >> .ci/linux-build.sh | 2 +- >> Documentation/faq/releases.rst | 8 ++++---- >> Documentation/intro/install/dpdk.rst | 8 ++++---- >> NEWS | 2 ++ >> 4 files changed, 11 insertions(+), 9 deletions(-) >> >> diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh index >> 863f02388..5323cb2f2 100755 >> --- a/.ci/linux-build.sh >> +++ b/.ci/linux-build.sh >> @@ -216,7 +216,7 @@ fi >> >> if [ "$DPDK" ] || [ "$DPDK_SHARED" ]; then >> if [ -z "$DPDK_VER" ]; then >> - DPDK_VER="20.11.1" >> + DPDK_VER="20.11.3" >> fi >> install_dpdk $DPDK_VER >> if [ "$CC" = "clang" ]; then >> diff --git a/Documentation/faq/releases.rst >> b/Documentation/faq/releases.rst index 68c9867b1..4f8d105e6 100644 >> --- a/Documentation/faq/releases.rst >> +++ b/Documentation/faq/releases.rst >> @@ -205,10 +205,10 @@ Q: What DPDK version does each Open vSwitch release >> work with? >> 2.10.x 17.11.10 >> 2.11.x 18.11.9 >> 2.12.x 18.11.9 >> - 2.13.x 19.11.8 >> - 2.14.x 19.11.8 >> - 2.15.x 20.11.1 >> - 2.16.x 20.11.1 >> + 2.13.x 19.11.10 >> + 2.14.x 19.11.10 >> + 2.15.x 20.11.3 >> + 2.16.x 20.11.3 >> ============ ======== >> >> Q: Are all the DPDK releases that OVS versions work with maintained? >> diff --git a/Documentation/intro/install/dpdk.rst >> b/Documentation/intro/install/dpdk.rst >> index 96843af73..83c758783 100644 >> --- a/Documentation/intro/install/dpdk.rst >> +++ b/Documentation/intro/install/dpdk.rst >> @@ -42,7 +42,7 @@ Build requirements >> In addition to the requirements described in :doc:`general`, building Open >> vSwitch with DPDK will require the following: >> >> -- DPDK 20.11.1 >> +- DPDK 20.11.3 >> >> - A `DPDK supported NIC`_ >> >> @@ -73,9 +73,9 @@ Install DPDK >> #. Download the `DPDK sources`_, extract the file and set ``DPDK_DIR``:: >> >> $ cd /usr/src/ >> - $ wget https://fast.dpdk.org/rel/dpdk-20.11.1.tar.xz >> - $ tar xf dpdk-20.11.1.tar.xz >> - $ export DPDK_DIR=/usr/src/dpdk-stable-20.11.1 >> + $ wget https://fast.dpdk.org/rel/dpdk-20.11.3.tar.xz >> + $ tar xf dpdk-20.11.3.tar.xz >> + $ export DPDK_DIR=/usr/src/dpdk-stable-20.11.3 >> $ cd $DPDK_DIR >> >> #. Configure and install DPDK using Meson diff --git a/NEWS b/NEWS >> index 90f4b1590..b92445a32 100644 >> --- a/NEWS >> +++ b/NEWS >> @@ -1,6 +1,8 @@ >> Post-v2.16.0 >> --------------------- >> - DPDK: >> + * OVS validated with DPDK 20.11.3. It is recommended to use this >> version >> + until further releases. >> * EAL argument --socket-mem is no longer configured by default upon >> start-up. If dpdk-socket-mem and dpdk-alloc-mem are not specified, >> DPDK defaults will be used. >> > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
