DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: ray.kinsella@intel.com, kuralamudhan.ramakrishnan@intel.com,
	louise.m.daly@intel.com, bruce.richardson@intel.com,
	ferruh.yigit@intel.com, konstantin.ananyev@intel.com
Subject: [dpdk-dev] [RFC 00/10] Support running DPDK without hugetlbfs mountpoint
Date: Thu, 31 May 2018 15:32:23 +0100	[thread overview]
Message-ID: <cover.1527776837.git.anatoly.burakov@intel.com> (raw)

This patchset takes old debug options "--huge-unlink" and
"--no-shconf" and replaces them both with a new option,
"--no-shared-files". This is a special mode which will
disable support for secondary processes, but which will
cause DPDK to not create any shared files while running -
neither hugepages nor any runtime data (everything will
be entirely in memory).

Additionally, on supported kernel/glibc versions (Linux
4.14+, glibc 2.27+), "--no-shared-files" mode will also
reserve hugepages using memfd instead of relying on
hugetlbfs mountpoint. This will make it possible to use
DPDK without hugetlbfs mountpoints (e.g. container use
cases).

This changes functionality of several command-line
switches, so RFC for now. Maybe we could leave the old
switches as they are and deprecate them in the next
release?

Anatoly Burakov (10):
  eal: add --no-shared-files option
  eal: make --no-shconf an alias for --no-shared-files
  eal: make --huge-unlink an alias for --no-shared-files
  fbarray: support no-shared-files mode
  mem: add support for no-shared-files mode
  ipc: add support for no-shared-files mode
  eal: add support for no-shared-files for hugepage info
  eal: add support for no-shared-files in hugepage data file
  eal: do not create runtime dir in no-shared-files mode
  mem: enable memfd-based hugepage allocation

 lib/librte_eal/bsdapp/eal/eal.c               |   7 +-
 lib/librte_eal/bsdapp/eal/eal_hugepage_info.c |   4 +
 lib/librte_eal/common/eal_common_fbarray.c    |  71 +++++----
 lib/librte_eal/common/eal_common_memory.c     |   3 +-
 lib/librte_eal/common/eal_common_options.c    |  25 ++--
 lib/librte_eal/common/eal_common_proc.c       |  25 ++++
 lib/librte_eal/common/eal_internal_cfg.h      |   3 +-
 lib/librte_eal/common/eal_options.h           |   7 +-
 lib/librte_eal/linuxapp/eal/eal.c             |  18 ++-
 .../linuxapp/eal/eal_hugepage_info.c          | 140 ++++++++++++++----
 lib/librte_eal/linuxapp/eal/eal_memalloc.c    | 126 +++++++++++++++-
 lib/librte_eal/linuxapp/eal/eal_memfd.h       |  28 ++++
 lib/librte_eal/linuxapp/eal/eal_memory.c      |  19 ++-
 test/test/test_eal_flags.c                    |  18 +--
 14 files changed, 384 insertions(+), 110 deletions(-)
 create mode 100644 lib/librte_eal/linuxapp/eal/eal_memfd.h

-- 
2.17.0

             reply	other threads:[~2018-05-31 14:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 14:32 Anatoly Burakov [this message]
2018-05-31 14:32 ` [dpdk-dev] [RFC 01/10] eal: add --no-shared-files option Anatoly Burakov
2018-05-31 14:32 ` [dpdk-dev] [RFC 02/10] eal: make --no-shconf an alias for --no-shared-files Anatoly Burakov
2018-05-31 14:32 ` [dpdk-dev] [RFC 03/10] eal: make --huge-unlink " Anatoly Burakov
2018-05-31 14:32 ` [dpdk-dev] [RFC 04/10] fbarray: support no-shared-files mode Anatoly Burakov
2018-05-31 14:32 ` [dpdk-dev] [RFC 05/10] mem: add support for " Anatoly Burakov
2018-05-31 14:32 ` [dpdk-dev] [RFC 06/10] ipc: " Anatoly Burakov
2018-05-31 14:32 ` [dpdk-dev] [RFC 07/10] eal: add support for no-shared-files for hugepage info Anatoly Burakov
2018-05-31 14:32 ` [dpdk-dev] [RFC 08/10] eal: add support for no-shared-files in hugepage data file Anatoly Burakov
2018-05-31 14:32 ` [dpdk-dev] [RFC 09/10] eal: do not create runtime dir in no-shared-files mode Anatoly Burakov
2018-05-31 14:32 ` [dpdk-dev] [RFC 10/10] mem: enable memfd-based hugepage allocation 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=cover.1527776837.git.anatoly.burakov@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=kuralamudhan.ramakrishnan@intel.com \
    --cc=louise.m.daly@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).