From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>
Subject: RE: [PATCH v2] common/mlx5: enable operation in iova virtual address mode
Date: Wed, 24 May 2023 14:04:28 +0000 [thread overview]
Message-ID: <MN2PR12MB30863B26774021A561CE2D63CF419@MN2PR12MB3086.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230412170723.20722-1-viacheslavo@nvidia.com>
Hi,
> -----Original Message-----
> From: Slava Ovsiienko <viacheslavo@nvidia.com>
> Sent: Wednesday, April 12, 2023 8:07 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Ori Kam <orika@nvidia.com>
> Subject: [PATCH v2] common/mlx5: enable operation in iova virtual address
> mode
>
> The ConnectX NIC series hardware provides advanced internal MMU option
> and can operate directly over virtual addresses, the host software should not
> care about any virtual-to-physical address translations. It means the mlx5
> PMDs can operate in DPDK IOVA VA (virtual address) mode transparently.
>
> To force IOVA VA mode the DPDK should be built with meson option:
>
> enable_iova_as_pa=false
>
> With this option only drivers supporting IOVA VA mode are enabled.
> This patch marks mlx5 drivers with require_iova_in_mbuf flag false value, thus
> allowing their compilation for IOVA VA mode.
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
>
> ---
> v1: http://patches.dpdk.org/project/dpdk/patch/20230412125320.8585-1-
> viacheslavo@nvidia.com/
> v2: fixed typos in commit message, reworded a little bit
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-05-24 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 12:53 [PATCH] common/mlx5: enable opration " Viacheslav Ovsiienko
2023-04-12 13:25 ` Morten Brørup
2023-04-12 17:07 ` [PATCH v2] common/mlx5: enable operation " Viacheslav Ovsiienko
2023-04-12 19:15 ` Morten Brørup
2023-05-24 14:04 ` 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=MN2PR12MB30863B26774021A561CE2D63CF419@MN2PR12MB3086.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@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).