Support running DPDK without hugetlbfs mountpoint
Status from this message: Applied, thanks.
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest8 patches 1 replyApplied
- v29 patches 5 repliesSuperseded
- v19 patches 0 repliesSuperseded
Changes in v3 from the cover letter
- Fix compile issue in patch 9 (now 8)
- Drop deprecation notice (will be sent separately)
Patches in v3 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | fbarray: support no-shconf modelib/ | +42 | 0 replies | |
| 2/8 | ipc: add support for no-shconf modelib/ | +25 | 0 replies | |
| 3/8 | eal: add support for no-shconf for hugepage infolib/ lib/ | +8 | 0 replies | |
| 4/8 | eal: add support for no-shconf in hugepage data filelib/ | +12 | 0 replies | |
| 5/8 | eal: do not create runtime dir in no-shconf modelib/ lib/ | +4 | 0 replies | |
| 6/8 | mem: add support for hugepage-unlink modelib/ lib/ | +21 | 0 replies | |
| 7/8 | eal: add --in-memory optionlib/ lib/ lib/ | +20 | 0 replies | |
| 8/8 | mem: support in-memory modelib/ lib/ lib/ | +149 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH v3 0/8] Support running DPDK without hugetlbfs mountpoint
This patchset adds a new command-line option "--in-memory", which takes old debug options "--huge-unlink" and "--no-shconf", and enhances them with additional functionality. This will allow DPDK to reserve hugepages anonymously instead of using hugetlbfs mountpoints. Coupled with the fact that this option also effectively enables both "--no-shconf" and "--huge-unlink" modes, DPDK will be able to run entirely in memory and not create any shared files while running - neither hugepages nor any runtime data.
This will, of course, disable secondary processes, but for use-cases this is targeted at (containers etc.), this is not a problem.
Older revisions had kernel support at 4.14+ and also required a fairly new glibc, but now due to not using memfd and using mmap() instead, minimum supported kernel version has dropped to 3.8.
v2->v3 changes:
- Fix compile issue in patch 9 (now 8)
- Drop deprecation notice (will be sent separately)
v1->v2 changes:
- Rebase on latest master
- Fix patch 5 to include check from patch 6 as commit message states
RFC->v1 changes:
- Dropped memfd, using anonymous mmap() instead
- Do not deprecate old command-line parameters, instead use them as they are, and add a deprecation notice to remove them in the next release.
Anatoly Burakov (8):
fbarray: support no-shconf mode
ipc: add support for no-shconf mode
eal: add support for no-shconf for hugepage info
eal: add support for no-shconf in hugepage data file
eal: do not create runtime dir in no-shconf mode
mem: add support for hugepage-unlink mode
eal: add --in-memory option
mem: support in-memory mode
lib/librte_eal/bsdapp/eal/eal.c | 3 +- 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_options.c | 20 ++- lib/librte_eal/common/eal_common_proc.c | 25 +++ lib/librte_eal/common/eal_internal_cfg.h | 4 + lib/librte_eal/common/eal_options.h | 2 + lib/librte_eal/linuxapp/eal/eal.c | 3 +- .../linuxapp/eal/eal_hugepage_info.c | 95 +++++++---- lib/librte_eal/linuxapp/eal/eal_memalloc.c | 150 ++++++++++++------ lib/librte_eal/linuxapp/eal/eal_memory.c | 16 +- 11 files changed, 276 insertions(+), 117 deletions(-)
Signature · 1 line
2.17.1