From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Wodkowski, PawelX" <pawelx.wodkowski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Wodkowski, PawelX" <pawelx.wodkowski@intel.com>
Subject: Re: [dpdk-dev] [RFC][PATCH] vfio: allow to map other memory regions
Date: Thu, 18 May 2017 11:23:43 +0000 [thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E451236978221513B@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <1495032287-216322-1-git-send-email-pawelx.wodkowski@intel.com>
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pawel Wodkowski
> Sent: Wednesday, May 17, 2017 3:45 PM
> To: dev@dpdk.org
> Cc: Wodkowski, PawelX <pawelx.wodkowski@intel.com>
> Subject: [dpdk-dev] [RFC][PATCH] vfio: allow to map other memory regions
>
> Currently it is not possible to use memory that is not owned by DPDK to
> perform DMA. This scenarion might be used in vhost applications (like
> SPDK) where guest send its own memory table. To fill this gap provide
> API to allow registering arbitrary address in VFIO container.
>
> Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com>
> ---
Seems to make sense to me. Presumably, such locally mapped memory would not work in multiprocess,
so, obvious as it may be, this should probably be documented.
Thanks,
Anatoly
next prev parent reply other threads:[~2017-05-18 11:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 14:44 Pawel Wodkowski
2017-05-17 17:20 ` Stephen Hemminger
2017-05-18 9:06 ` Wodkowski, PawelX
2017-05-18 11:23 ` Burakov, Anatoly [this message]
2017-05-23 13:53 ` [dpdk-dev] [PATCH v2] " Pawel Wodkowski
2017-05-23 13:59 ` [dpdk-dev] [PATCH v3] " Pawel Wodkowski
2017-05-24 11:17 ` [dpdk-dev] [PATCH] " Pawel Wodkowski
[not found] ` <1496663643-65002-1-git-send-email-pawelx.wodkowski@intel.com>
2017-06-05 8:16 ` Wodkowski, PawelX
2017-06-13 9:02 ` Burakov, Anatoly
2017-06-19 21:04 ` Thomas Monjalon
2017-06-28 9:54 ` Wodkowski, PawelX
2017-06-28 11:50 ` Thomas Monjalon
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=C6ECDF3AB251BE4894318F4E451236978221513B@IRSMSX109.ger.corp.intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=pawelx.wodkowski@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).