From: Raslan Darawsheh <rasland@nvidia.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [PATCH v2 0/5] Refactor mlx5 guides
Date: Wed, 23 Feb 2022 14:35:16 +0000 [thread overview]
Message-ID: <BYAPR12MB30783C66C7FD54B06368349ECF3C9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220223134834.2840916-1-michaelba@nvidia.com>
Hi,
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Wednesday, February 23, 2022 3:48 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH v2 0/5] Refactor mlx5 guides
>
> Recently [1] all the drivers running over the mlx5 device started sharing some
> objects.
> This raised the need to create documentation for the common driver that
> would contain information relevant to all drivers and in particular:
>
> - Tutorial for configuration of the device.
> - Instruction for using Mellanox ofed.
> - devargs of the common driver.
>
> This series adds such documentation and reference to it as parts of the
> documentation of the other drivers.
>
> [1]
> https://patchwork.dpdk.org/project/dpdk/cover/20211019205602.3188203-
> 1-michaelba@nvidia.com/
>
> v2: Rebase
>
>
> Michael Baum (5):
> doc: remove obsolete explanations from mlx5 guide
> doc: replace broken links in mlx5 guide
> doc: correct name of BlueField-2 in mlx5 guide
> doc: add shared guide for mlx5 PMDs
> doc: update doorbell mapping parameter name in mlx5 guide
>
> doc/guides/compressdevs/mlx5.rst | 40 +-
> doc/guides/cryptodevs/mlx5.rst | 38 +-
> doc/guides/nics/mlx4.rst | 4 +-
> doc/guides/nics/mlx5.rst | 567 +-----------------
> doc/guides/platform/index.rst | 1 +
> doc/guides/platform/mlx5.rst | 641 +++++++++++++++++++++
> doc/guides/regexdevs/mlx5.rst | 44 +-
> doc/guides/vdpadevs/mlx5.rst | 87 +--
> drivers/common/mlx5/linux/mlx5_common_os.c | 2 +-
> drivers/common/mlx5/mlx5_common.c | 31 +-
> drivers/common/mlx5/mlx5_common_defs.h | 8 +-
> drivers/net/mlx5/linux/mlx5_verbs.c | 2 +-
> drivers/net/mlx5/mlx5_devx.c | 2 +-
> 13 files changed, 747 insertions(+), 720 deletions(-) create mode 100644
> doc/guides/platform/mlx5.rst
>
> --
> 2.25.1
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-02-23 14:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 12:48 [PATCH 0/5] refactore " Michael Baum
2022-02-22 12:48 ` [PATCH 1/5] doc: remove obsolete explanations from mlx5 guide Michael Baum
2022-02-22 12:48 ` [PATCH 2/5] doc: replace broken links in " Michael Baum
2022-02-22 12:48 ` [PATCH 3/5] doc: correct name of BlueField-2 " Michael Baum
2022-02-22 12:48 ` [PATCH 4/5] doc: add shared guide for mlx5 PMDs Michael Baum
2022-02-22 12:48 ` [PATCH 5/5] doc: update doorbell mapping parameter name in mlx5 guide Michael Baum
2022-02-22 14:43 ` [PATCH 0/5] refactore mlx5 guides Raslan Darawsheh
2022-02-23 13:48 ` [PATCH v2 0/5] Refactor " Michael Baum
2022-02-23 13:48 ` [PATCH v2 1/5] doc: remove obsolete explanations from mlx5 guide Michael Baum
2022-02-23 13:48 ` [PATCH v2 2/5] doc: replace broken links in " Michael Baum
2022-02-23 13:48 ` [PATCH v2 3/5] doc: correct name of BlueField-2 " Michael Baum
2022-02-23 13:48 ` [PATCH v2 4/5] doc: add shared guide for mlx5 PMDs Michael Baum
2022-02-23 13:48 ` [PATCH v2 5/5] doc: update doorbell mapping parameter name in mlx5 guide Michael Baum
2022-02-23 21:48 ` Ferruh Yigit
2022-02-25 0:01 ` Michael Baum
2022-02-25 10:21 ` Ferruh Yigit
2022-02-23 14:35 ` Raslan Darawsheh [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=BYAPR12MB30783C66C7FD54B06368349ECF3C9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=viacheslavo@nvidia.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).