Darrell Ball <db...@vmware.com> writes:

> -----Original Message-----
> From: <ovs-dev-boun...@openvswitch.org> on behalf of Michal Weglicki 
> <michalx.wegli...@intel.com>
> Date: Tuesday, July 25, 2017 at 5:34 AM
> To: "d...@openvswitch.org" <d...@openvswitch.org>
> Subject: [ovs-dev] [PATCH v4] Update relevant artifacts to add support for    
> DPDK 17.05.1.
>
>     Upgrading to DPDK 17.05.1 stable release adds new
>     significant features relevant to OVS, including,
>     but not limited to:
>     - tun/tap PMD,
>     - VFIO hotplug support,
>     - Generic flow API.
>     
>     Following changes are applied:
>     - netdev-dpdk: Changes required by DPDK API modifications.
>     - doc: Because of DPDK API changes, backward compatibility
>       with previous DPDK releases will be broken, thus all
>       relevant documentation entries are updated.
>     - .travis: DPDK version change from 16.11.1 to 17.05.1.
>     - rhel/openvswitch-fedora.spec.in: DPDK version change
>       from 16.11 to 17.05.1
>     
>     v1->v2: Patch rebase.
>     v2->v3: Fixed wrong formating after v2 patch rebase.
>     v3->v4: Minor documentation changes.
>     
>     Signed-off-by: Michal Weglicki <michalx.wegli...@intel.com>
>     Reviewed-by: Aaron Conole <acon...@redhat.com>
>     ---
>      .travis/linux-build.sh                   |   2 +-
>      Documentation/faq/releases.rst           |   1 +
>      Documentation/howto/dpdk.rst             |   6 +-
>      Documentation/intro/install/dpdk.rst     |  14 +--
>      Documentation/topics/dpdk/vhost-user.rst |  12 +--
>      NEWS                                     |   1 +
>      lib/netdev-dpdk.c                        | 144 
> +++++++++++++++++++------------
>      rhel/openvswitch-fedora.spec.in          |   2 +-
>      tests/dpdk/ring_client.c                 |   6 +-
>      9 files changed, 114 insertions(+), 74 deletions(-)
>     
>     diff --git a/.travis/linux-build.sh b/.travis/linux-build.sh
>     index f66b534..efccdf1 100755
>     --- a/.travis/linux-build.sh
>     +++ b/.travis/linux-build.sh
>     @@ -80,7 +80,7 @@ fi
>      
>      if [ "$DPDK" ]; then
>          if [ -z "$DPDK_VER" ]; then
>     -        DPDK_VER="16.11.2"
>     +        DPDK_VER="17.05.1"
>          fi
>          install_dpdk $DPDK_VER
>          if [ "$CC" = "clang" ]; then
>     diff --git a/Documentation/faq/releases.rst 
> b/Documentation/faq/releases.rst
>     index 707834b..2ecc24c 100644
>     --- a/Documentation/faq/releases.rst
>     +++ b/Documentation/faq/releases.rst
>     @@ -161,6 +161,7 @@ Q: What DPDK version does each Open vSwitch release 
> work with?
>          2.5.x        2.2
>          2.6.x        16.07.2
>          2.7.x        16.11.2
>     +    2.8.x        17.05.1
>          ============ =======
>      
>      Q: I get an error like this when I configure Open vSwitch:
>     diff --git a/Documentation/howto/dpdk.rst b/Documentation/howto/dpdk.rst
>     index af01d3e..1756c8c 100644
>     --- a/Documentation/howto/dpdk.rst
>     +++ b/Documentation/howto/dpdk.rst
>     @@ -528,15 +528,15 @@ described in :ref:`dpdk-testpmd`. Once compiled, 
> run the application::
>      
>      When you finish testing, bind the vNICs back to kernel::
>      
>     -    $ $DPDK_DIR/tools/dpdk-devbind.py --bind=virtio-pci 0000:00:03.0
>     -    $ $DPDK_DIR/tools/dpdk-devbind.py --bind=virtio-pci 0000:00:04.0
>     +    $ $DPDK_DIR/usertools/dpdk-devbind.py --bind=virtio-pci 0000:00:03.0
>     +    $ $DPDK_DIR/usertools/dpdk-devbind.py --bind=virtio-pci 0000:00:04.0
>      
>      .. note::
>      
>        Valid PCI IDs must be passed in above example. The PCI IDs can be 
> retrieved
>        like so::
>      
>     -      $ $DPDK_DIR/tools/dpdk-devbind.py --status
>     +      $ $DPDK_DIR/usertools/dpdk-devbind.py --status
>      
>      More information on the dpdkvhostuser ports can be found in
>      :doc:`/topics/dpdk/vhost-user`.
>
> [Darrell]
> While dealing with something else, I noticed that this file has an outdated 
> reference,
> as of OVS 2.8/DPDK 17.05.1, to VFIO not supporting hotplug. Specifically, the 
> text 
>
> “This feature is not supported with VFIO” under “Port Hotplug”
>
> It will be removed unless someone objects.
>
> //////////////////

That makes sense.

OTOH, how is it going to work as far as applying / pulling / etc. goes?

I know that the DPDK related work is planning on going with a
pull-request model.  Does that mean this patch is applied to your branch
and you will submit a pull request with it at some point?  How about
work that builds on this patch?  As an example,
  https://mail.openvswitch.org/pipermail/ovs-dev/2017-July/335250.html

I'd like to submit my latest work for this series, but not sure where or
how.

-Aaron
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to