From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
dev <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>,
Xuan Ding <xuan.ding@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/1] vfio: add page-by-page mapping API
Date: Mon, 3 Jul 2023 16:48:57 -0700 [thread overview]
Message-ID: <20230703164857.6b016eab@hermes.local> (raw)
In-Reply-To: <CAJFAV8whkYmE7n-H4usUdYqq0FSbQ5x=Nd9fQzNzAQh4WzCEow@mail.gmail.com>
On Thu, 2 Jun 2022 10:23:07 +0200
David Marchand <david.marchand@redhat.com> wrote:
> Hello Anatoly,
>
> On Tue, Nov 2, 2021 at 4:54 PM Burakov, Anatoly
> <anatoly.burakov@intel.com> wrote:
> >
> > On 28-Oct-21 3:09 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>
> > > ---
> > >
> > > Notes:
> > > v2:
> > > - Added checks for page alignment of supplied values
> > > - Added rte_errno values (similar to patch 103165 [1])
> > >
> > > [1] http://patches.dpdk.org/project/dpdk/patch/e8c5e7ba089e2283c3cd67e4529e52fe49390eb9.1635428963.git.anatoly.burakov@intel.com/
> >
> > I think this API also needs VA and IOVA addresses in an array, so that
> > it's possible to map IOVA-discontiguous segments. This is too late for
> > this release, so let's postpone it till 22.02.
>
> It seems this patch fell through the cracks.
> Any update?
>
> Thanks.
It is not clear what problem this is trying to solve.
Is it for some hardware platform that is not available?
Any updates on this patch or should it just be dropped?
next prev parent reply other threads:[~2023-07-03 23:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 11:27 [dpdk-dev] [PATCH v1 " Anatoly Burakov
2021-09-10 12:31 ` Burakov, Anatoly
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 [this message]
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=20230703164857.6b016eab@hermes.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.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).