From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, tiwei.bie@intel.com, zhihong.wang@intel.com,
anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/4] Add external contiguous memory support to Virtio-user
Date: Fri, 25 Aug 2023 11:55:23 +0200 [thread overview]
Message-ID: <CAJFAV8wdxxjzS0HjuspL59ko_DA7ohNTjCvOktD7T2hcvNbOxw@mail.gmail.com> (raw)
In-Reply-To: <20191213141322.32730-1-maxime.coquelin@redhat.com>
On Fri, Dec 13, 2019 at 3:13 PM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
>
> Somme applications/frameworks using DPDK allocate their own memory
> for its buffers. This is the case of Seastar, and also VPP.
>
> It is currently not possible to use Virtio-user PMD with these
> applications because Virtio-user requires file descriptor for this
> memory to be shared with the vhost-user backend (vDPA in our case [0]).
>
> This series introduces a new API in EAL to register external memory
> that is contiguous in both the VA and the IOVA space.
>
> It also enables VDEVs to implement the DMA map/unmap callback, and
> implement it in Virtio-user PMD.
>
> Please note that extmem unit tests are missing. I'm working on it
> and it will be in v2. Just share this v1 for early reviews.
>
> Maxime Coquelin (4):
> eal: add new API to register contiguous external memory
> eal: allow getting memory segment FD with external memory
> bus/vdev: add DMA mapping supprt
> net/virtio: add DMA mapping callback to virtio-user
>
> drivers/bus/vdev/rte_bus_vdev.h | 24 +++++
> drivers/bus/vdev/vdev.c | 50 +++++++++++
> .../net/virtio/virtio_user/virtio_user_dev.c | 10 +--
> .../net/virtio/virtio_user/virtio_user_dev.h | 3 +
> drivers/net/virtio/virtio_user_ethdev.c | 58 +++++++++++++
> lib/librte_eal/common/eal_common_memory.c | 87 ++++++++++++++++---
> lib/librte_eal/common/include/rte_memory.h | 46 ++++++++++
> lib/librte_eal/common/malloc_heap.c | 17 +++-
> lib/librte_eal/common/malloc_heap.h | 2 +-
> lib/librte_eal/common/rte_malloc.c | 2 +-
> lib/librte_eal/rte_eal_version.map | 3 +
> 11 files changed, 278 insertions(+), 24 deletions(-)
I am not sure this feature is still needed as there was no activity
for a long time.
There was some feedback from Anatoly and the series needs a rebase in any case.
I marked the series as Changes requested so it is clear it can't be
considered for merging in its current state.
Thanks.
--
David Marchand
prev parent reply other threads:[~2023-08-25 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 14:13 Maxime Coquelin
2019-12-13 14:13 ` [dpdk-dev] [PATCH 1/4] eal: add new API to register contiguous external memory Maxime Coquelin
2020-01-23 13:06 ` Burakov, Anatoly
2019-12-13 14:13 ` [dpdk-dev] [PATCH 2/4] eal: allow getting memory segment FD with " Maxime Coquelin
2019-12-13 14:13 ` [dpdk-dev] [PATCH 3/4] bus/vdev: add DMA mapping supprt Maxime Coquelin
2019-12-13 14:13 ` [dpdk-dev] [PATCH 4/4] net/virtio: add DMA mapping callback to virtio-user Maxime Coquelin
2020-01-08 16:11 ` [dpdk-dev] [PATCH 0/4] Add external contiguous memory support to Virtio-user Maxime Coquelin
2023-08-25 9:55 ` David Marchand [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=CAJFAV8wdxxjzS0HjuspL59ko_DA7ohNTjCvOktD7T2hcvNbOxw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=zhihong.wang@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).