DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tom Barbette <barbette@kth.se>
To: Shahaf Shuler <shahafs@mellanox.com>,
	john.mcnamara@intel.com, marko.kovacevic@intel.com
Cc: dev@dpdk.org, erezsc@mellanox.com, olgas@mellanox.com,
	yskoh@mellanox.com
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: update Mellanox supported OFED version
Date: Thu, 14 Mar 2019 12:20:18 +0100	[thread overview]
Message-ID: <19660f3d-6735-1689-4de6-a4f4fd173f52@kth.se> (raw)
In-Reply-To: <20181119124645.11705-2-shahafs@mellanox.com>

A bit of an old thread, but I just tried to update the OFED 4.5 as this 
doc patch suggests and DPDK (19.02 or master) do not compile anymore for 
mlx5?

Was the doc updated too soon or should I do something special to clean 
4.4 and update 4.5?

I did install the OFED with --upsteam-libs and --dpdk (4.4 works fine).

Error sample:
In file included from /usr/include/infiniband/mlx5dv.h:48:0,
                  from 
/home/tom/dpdk-skylake/drivers/net/mlx5/mlx5_glue.c:21:
/home/tom/dpdk-skylake/drivers/net/mlx5/mlx5_glue.h:54:6: error: nested 
redefinition of ‘enum mlx5_ib_uapi_flow_action_packet_reformat_type’
  enum mlx5dv_flow_action_packet_reformat_type { packet_reformat_type = 
0, };
       ^
/home/tom/dpdk-skylake/drivers/net/mlx5/mlx5_glue.h:54:6: error: 
redeclaration of ‘enum mlx5_ib_uapi_flow_action_packet_reformat_type’
In file included from /usr/include/infiniband/mlx5_api.h:36:0,
                  from /usr/include/infiniband/mlx5dv.h:48,
                  from 
/home/tom/dpdk-skylake/drivers/net/mlx5/mlx5_glue.c:21:


On 2018-11-19 13:46, Shahaf Shuler wrote:
> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> ---
>   doc/guides/nics/mlx4.rst | 2 +-
>   doc/guides/nics/mlx5.rst | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
> index 4a57c7a6aa..5326d916e1 100644
> --- a/doc/guides/nics/mlx4.rst
> +++ b/doc/guides/nics/mlx4.rst
> @@ -213,7 +213,7 @@ Current RDMA core package and Linux kernel (recommended)
>   Mellanox OFED as a fallback
>   ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   
> -- `Mellanox OFED`_ version: **4.3, 4.4**.
> +- `Mellanox OFED`_ version: **4.4, 4.5**.
>   - firmware version: **2.42.5000** and above.
>   
>   .. _`Mellanox OFED`: http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
> index 3610e00862..b52f8af708 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -557,7 +557,7 @@ RMDA Core with Linux Kernel
>   Mellanox OFED
>   ^^^^^^^^^^^^^
>   
> -- Mellanox OFED version: **4.3, 4.4**.
> +- Mellanox OFED version: **4.4, 4.5**.
>   - firmware version:
>   
>     - ConnectX-4: **12.21.1000** and above.
> 

  reply	other threads:[~2019-03-14 11:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 12:46 [dpdk-dev] [PATCH 1/2] doc: update Mellanox release notes Shahaf Shuler
2018-11-19 12:46 ` [dpdk-dev] [PATCH 2/2] doc: update Mellanox supported OFED version Shahaf Shuler
2019-03-14 11:20   ` Tom Barbette [this message]
2019-03-14 11:20     ` Tom Barbette
2019-03-17 15:27     ` Ali Alnubani
2019-03-17 15:27       ` Ali Alnubani
2019-03-19  9:34       ` Tom Barbette
2019-03-19  9:34         ` Tom Barbette
2019-03-20 12:54         ` Ali Alnubani
2019-03-20 12:54           ` Ali Alnubani
2019-03-20 17:13           ` Tom Barbette
2019-03-20 17:13             ` Tom Barbette
2019-05-14  8:43             ` Tom Barbette
2019-05-14  8:43               ` Tom Barbette
2018-11-21 14:52 ` [dpdk-dev] [PATCH 1/2] doc: update Mellanox release notes Ferruh Yigit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19660f3d-6735-1689-4de6-a4f4fd173f52@kth.se \
    --to=barbette@kth.se \
    --cc=dev@dpdk.org \
    --cc=erezsc@mellanox.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=olgas@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=yskoh@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).