DPDK patches and discussions
 help / color / mirror / Atom feed
From: Long Li <longli@microsoft.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"longli@linuxonhyperv.com" <longli@linuxonhyperv.com>
Cc: Ferruh Yigit <ferruh.yigit@xilinx.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Ajay Sharma <sharmaajay@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>
Subject: RE: [Patch v2 01/17] net/mana: add basic driver, build environment and doc
Date: Wed, 6 Jul 2022 16:07:34 +0000	[thread overview]
Message-ID: <MN0PR21MB326487236B19F7B0744551F7CE809@MN0PR21MB3264.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20220706080940.30299e2f@hermes.local>

> Subject: Re: [Patch v2 01/17] net/mana: add basic driver, build environment and
> doc
> 
> On Tue,  5 Jul 2022 17:28:32 -0700
> longli@linuxonhyperv.com wrote:
> 
> > +Prerequisites
> > +-------------
> > +
> > +This driver relies on external libraries and kernel drivers for
> > +resources allocations and initialization. The following dependencies
> > +are not part of DPDK and must be installed separately:
> > +
> > +- **libibverbs** (provided by rdma-core package)
> > +
> 
> Is there a version dependency on rdma-core? Is that version dependency listed
> somewhere?

The rdma-core and kernel drivers are being submitted. The expected version supporting MANA is with rdma-core v42 and Linux 5.19 (or 5.20).

I'm not sure if there is a way to enforce meson to build on a certain rdma-core or kernel version. Is it okay to add the following information to doc/guides/nics/mana.rst for specifying the version requirement?


Current RDMA core package and Linux kernel
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

- Minimal Linux kernel version: 5.19.
- Minimal RDMA core version: v42 (see `RDMA core installation documentation`_).

.. _`RDMA core installation documentation`: https://raw.githubusercontent.com/linux-rdma/rdma-core/master/README.md

  reply	other threads:[~2022-07-06 16:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06  0:28 [Patch v2 00/17] Introduce Microsoft Azure Network Adatper (MANA) PMD longli
2022-07-06  0:28 ` [Patch v2 01/17] net/mana: add basic driver, build environment and doc longli
2022-07-06 15:09   ` Stephen Hemminger
2022-07-06 16:07     ` Long Li [this message]
2022-07-06 16:19       ` David Marchand
2022-07-06 16:25         ` Long Li
2022-07-06  0:28 ` [Patch v2 02/17] net/mana: add device configuration and stop longli
2022-07-06  0:28 ` [Patch v2 03/17] net/mana: add function to report support ptypes longli
2022-07-06  0:28 ` [Patch v2 04/17] net/mana: add link update longli
2022-07-06  0:28 ` [Patch v2 05/17] net/mana: add function for device removal interrupts longli
2022-07-06  0:28 ` [Patch v2 06/17] net/mana: add device info longli
2022-07-06  0:28 ` [Patch v2 07/17] net/mana: add function to configure RSS longli
2022-07-06  0:28 ` [Patch v2 08/17] net/mana: add function to configure RX queues longli
2022-07-06  0:28 ` [Patch v2 09/17] net/mana: add function to configure TX queues longli
2022-07-06  0:28 ` [Patch v2 10/17] net/mana: implement memory registration longli
2022-07-06  0:28 ` [Patch v2 11/17] net/mana: implement the hardware layer operations longli
2022-07-06  0:28 ` [Patch v2 12/17] net/mana: add function to start/stop TX queues longli
2022-07-06  0:28 ` [Patch v2 13/17] net/mana: add function to start/stop RX queues longli
2022-07-06  0:28 ` [Patch v2 14/17] net/mana: add function to receive packets longli
2022-07-06  0:28 ` [Patch v2 15/17] net/mana: add function to send packets longli
2022-07-06  0:28 ` [Patch v2 16/17] net/mana: add function to start/stop device longli
2022-07-06  0:28 ` [Patch v2 17/17] net/mana: add function to report queue stats longli

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=MN0PR21MB326487236B19F7B0744551F7CE809@MN0PR21MB3264.namprd21.prod.outlook.com \
    --to=longli@microsoft.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=longli@linuxonhyperv.com \
    --cc=sharmaajay@microsoft.com \
    --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).