From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org,
Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>,
Omar Cardona <ocardona@microsoft.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>,
Ranjit Menon <ranjit.menon@intel.com>,
Tal Shnaiderman <talshn@mellanox.com>,
Fady Bader <fady@mellanox.com>, Ophir Munk <ophirmu@mellanox.com>,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [Minutes 04/15/2020] Bi-Weekly DPDK Windows Community Call
Date: Fri, 17 Apr 2020 18:10:36 +0300 [thread overview]
Message-ID: <20200417181036.7b2fe027@Sovereign> (raw)
In-Reply-To: <6962862.uKWtJMOXK1@thomas>
> > 4. Device can be VA-only with an onboard IOMMU (e.g. Mellanox NICs).
>
> Mellanox NICs work also with PA memory.
IIRC, you told us there's something special with Mellanox NICs and IOMMU.
Documentation says (https://doc.dpdk.org/guides/nics/mlx5.html):
For security reasons and robustness, this driver only deals with
virtual memory addresses. The way resources allocations are handled
by the kernel, combined with hardware specifications that allow to
handle virtual memory addresses directly, ensure that DPDK
applications cannot access random physical memory (or memory that
does not belong to the current process).
> DMA_ADAPTER and DMA_IOMMU are kernel interfaces, without any userspace API?
Correct.
--
Dmitry Kozlyuk
prev parent reply other threads:[~2020-04-17 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 21:02 [dpdk-dev] Fwd: " Thomas Monjalon
2020-04-16 23:46 ` [dpdk-dev] " Dmitry Kozlyuk
2020-04-17 7:47 ` Thomas Monjalon
2020-04-17 15:10 ` Dmitry Kozlyuk [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=20200417181036.7b2fe027@Sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=dmitrym@microsoft.com \
--cc=fady@mellanox.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=ocardona@microsoft.com \
--cc=ophirmu@mellanox.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@mellanox.com \
--cc=thomas@monjalon.net \
/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).