From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [RFC] mlx5: update NIC documentation on RDMA core version
Date: Thu, 4 Jan 2018 08:54:54 +0100 [thread overview]
Message-ID: <20180104075454.kegvl2lb76f2q7go@shalom> (raw)
In-Reply-To: <20180103072330.2f0d4d48@xeon-e3>
On Wed, Jan 03, 2018 at 07:23:30AM -0800, Stephen Hemminger wrote:
> On Wed, 3 Jan 2018 08:52:01 +0100
> Nelio Laranjeiro <nelio.laranjeiro@6wind.com> wrote:
>
> > Hi Stephen,
> >
> > Seems you missed an important point, MLNX_OFED is still supported with
> > this driver allowing it to work on stable releases like strict debian 9
> > i.e. without updating the Linux kernel.
>
> So the documentation should reflect the two possibilities more clearly.
>
> OFED version > ??
> or RDMA core version >= 16
>
> The current documentation is unclear and doesn't help the users.
It is explained in the section "21.5.1. Installation" [1] of the mlx5
documentation.
I am not against modifying the documentation to make it more clearer,
but we need to keep both information MLNX_OFED with un-modified
distributions or Linux Kernel upstream with RDMA-Core for those who have
modified their Linux Kernel.
Thanks,
[1] http://dpdk.org/doc/guides/nics/mlx5.html#installation
--
Nélio Laranjeiro
6WIND
prev parent reply other threads:[~2018-01-04 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 21:44 Stephen Hemminger
2018-01-03 7:52 ` Nelio Laranjeiro
2018-01-03 15:23 ` Stephen Hemminger
2018-01-04 7:54 ` Nélio Laranjeiro [this message]
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=20180104075454.kegvl2lb76f2q7go@shalom \
--to=nelio.laranjeiro@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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).