From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>,
"Ray Kinsella" <mdr@ashroe.eu>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>
Cc: <xuan.ding@intel.com>, <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1 1/1] vfio: add page-by-page mapping API
Date: Fri, 10 Sep 2021 13:31:10 +0100 [thread overview]
Message-ID: <90bf1977-4828-3992-531a-1bd3591f200d@intel.com> (raw)
In-Reply-To: <043fc2d53770da8248b9cd0214775f9d41f2e0fb.1631273229.git.anatoly.burakov@intel.com>
On 10-Sep-21 12:27 PM, Anatoly Burakov wrote:
> Currently, there is no way to map memory for DMA in a way that allows
> unmapping it partially later, because some IOMMU's do not support
> partial unmapping. There is a workaround of mapping all of these
> segments separately, but this is inconvenient and silly, so this
> commit adds a proper API that does it.
>
> This commit relies on earlier infrastructure that was built out to
> support "chunking", as the concept of "chunks" is essentially the same
> as page size.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
This patch depends on Xuan's VFIO chunking patchset [1].
[1] http://patches.dpdk.org/project/dpdk/list/?series=18590
--
Thanks,
Anatoly
next prev parent reply other threads:[~2021-09-10 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 11:27 Anatoly Burakov
2021-09-10 12:31 ` Burakov, Anatoly [this message]
2021-09-29 10:18 ` Burakov, Anatoly
2021-10-28 8:18 ` David Marchand
2021-10-28 13:00 ` Burakov, Anatoly
2021-10-28 14:09 ` [dpdk-dev] [PATCH v2 " Anatoly Burakov
2021-11-02 15:16 ` Burakov, Anatoly
2022-06-02 8:23 ` David Marchand
2023-07-03 23:48 ` Stephen Hemminger
2023-07-04 12:51 ` Burakov, Anatoly
2022-06-02 9:14 ` Ray Kinsella
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=90bf1977-4828-3992-531a-1bd3591f200d@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=ferruh.yigit@intel.com \
--cc=mdr@ashroe.eu \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=xuan.ding@intel.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).