From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Viacheslav Ovsiienko" <viacheslavo@nvidia.com>, <dev@dpdk.org>
Cc: <matan@nvidia.com>, <rasland@nvidia.com>, <orika@nvidia.com>
Subject: RE: [PATCH] common/mlx5: enable opration in iova virtual address mode
Date: Wed, 12 Apr 2023 15:25:10 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87868@smartserver.smartshare.dk> (raw)
In-Reply-To: <20230412125320.8585-1-viacheslavo@nvidia.com>
> From: Viacheslav Ovsiienko [mailto:viacheslavo@nvidia.com]
> Sent: Wednesday, 12 April 2023 14.53
>
> The ConnectX NIC series hardware provides the advanced internal
> MMU option and can operate directly ob virtual addresses, host
> software should not do 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,
> thus allowing their compilation for IOVA VA mode.
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
Excellent.
Acked-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2023-04-12 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 12:53 Viacheslav Ovsiienko
2023-04-12 13:25 ` Morten Brørup [this message]
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
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=98CBD80474FA8B44BF855DF32C47DC35D87868@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@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).