From: Tiwei Bie <tiwei.bie@intel.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, przemyslawx.lal@intel.com,
kuralamudhan.ramakrishnan@intel.com, ivan.coughlan@intel.com,
ray.kinsella@intel.com, maxime.coquelin@redhat.com
Subject: Re: [dpdk-dev] [PATCH v2 0/5] Allow using virtio without hugepages
Date: Thu, 13 Dec 2018 12:53:58 +0800 [thread overview]
Message-ID: <20181213045358.GA26505@dpdk-tbie.sh.intel.com> (raw)
In-Reply-To: <cover.1544546363.git.anatoly.burakov@intel.com>
On Tue, Dec 11, 2018 at 04:43:27PM +0000, Anatoly Burakov wrote:
> It is already possible to use both DPDK in general and
> virtio specifically, without hugetlbfs mounts, but
> currently virtio cannot be used without hugepage memory
> (i.e. with a --no-huge EAL switch) due to the fact that
> it needs to share memory with the backend.
>
> This patchset uses memfd to create actual files backing
> anonymous memory. This enabled virtio to work not only
> without hugetlbfs, but without hugepages altogether,
> which could be useful in Cloud Native scenarios.
Nice work!
Acked-by: Tiwei Bie <tiwei.bie@intel.com>
>
> v2:
> - Fixed segment fd list not being initialized
> - Added some segment fd API fixes
> - Added unit test for segment fd API
>
> Anatoly Burakov (5):
> mem: fix error code for segment fd API for external segs
> memalloc: check for memfd support in segment fd API
> memalloc: allow setting up segment list fd's
> mem: use memfd for no-huge mode
> test: add segment fd API test
>
> doc/guides/rel_notes/release_19_02.rst | 13 +++++
> lib/librte_eal/bsdapp/eal/eal_memalloc.c | 6 ++
> lib/librte_eal/common/eal_common_memory.c | 12 ++++
> lib/librte_eal/common/eal_memalloc.h | 4 ++
> lib/librte_eal/linuxapp/eal/eal_memalloc.c | 66 +++++++++++++++++++---
> lib/librte_eal/linuxapp/eal/eal_memory.c | 54 +++++++++++++++++-
> test/test/test_memory.c | 43 ++++++++++++++
> 7 files changed, 188 insertions(+), 10 deletions(-)
>
> --
> 2.17.1
next prev parent reply other threads:[~2018-12-13 4:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 17:54 [dpdk-dev] [PATCH 19.02 0/2] " Anatoly Burakov
2018-11-13 17:54 ` [dpdk-dev] [PATCH 19.02 1/2] memalloc: allow setting up segment list fd's Anatoly Burakov
2018-11-13 17:54 ` [dpdk-dev] [PATCH 19.02 2/2] mem: use memfd for no-huge mode Anatoly Burakov
2018-11-28 4:57 ` Tiwei Bie
2018-11-28 9:11 ` Burakov, Anatoly
2018-12-11 16:43 ` [dpdk-dev] [PATCH v2 0/5] Allow using virtio without hugepages Anatoly Burakov
2018-12-13 4:53 ` Tiwei Bie [this message]
2018-12-13 11:43 ` [dpdk-dev] [PATCH v3 0/5] Allow using virtio-user " Anatoly Burakov
2018-12-20 22:01 ` Thomas Monjalon
2018-12-13 11:43 ` [dpdk-dev] [PATCH v3 1/5] mem: fix error code for segment fd API for external segs Anatoly Burakov
2018-12-14 9:15 ` Maxime Coquelin
2018-12-13 11:43 ` [dpdk-dev] [PATCH v3 2/5] memalloc: check for memfd support in segment fd API Anatoly Burakov
2018-12-14 9:19 ` Maxime Coquelin
2018-12-13 11:43 ` [dpdk-dev] [PATCH v3 3/5] memalloc: allow setting up segment list fd's Anatoly Burakov
2018-12-14 10:03 ` Maxime Coquelin
2018-12-13 11:43 ` [dpdk-dev] [PATCH v3 4/5] mem: use memfd for no-huge mode Anatoly Burakov
2018-12-13 11:59 ` Burakov, Anatoly
2018-12-14 10:06 ` Maxime Coquelin
2018-12-13 11:43 ` [dpdk-dev] [PATCH v3 5/5] test: add segment fd API test Anatoly Burakov
2018-12-14 10:09 ` Maxime Coquelin
2018-12-11 16:43 ` [dpdk-dev] [PATCH v2 1/5] mem: fix error code for segment fd API for external segs Anatoly Burakov
2018-12-11 16:43 ` [dpdk-dev] [PATCH v2 2/5] memalloc: check for memfd support in segment fd API Anatoly Burakov
2018-12-11 16:43 ` [dpdk-dev] [PATCH v2 3/5] memalloc: allow setting up segment list fd's Anatoly Burakov
2018-12-11 16:43 ` [dpdk-dev] [PATCH v2 4/5] mem: use memfd for no-huge mode Anatoly Burakov
2018-12-13 4:59 ` Tiwei Bie
2018-12-13 11:36 ` Burakov, Anatoly
2018-12-11 16:43 ` [dpdk-dev] [PATCH v2 5/5] test: add segment fd API test Anatoly Burakov
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=20181213045358.GA26505@dpdk-tbie.sh.intel.com \
--to=tiwei.bie@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ivan.coughlan@intel.com \
--cc=kuralamudhan.ramakrishnan@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=przemyslawx.lal@intel.com \
--cc=ray.kinsella@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).