diff options
author | 2017-04-19 14:28:47 +0200 | |
---|---|---|
committer | 2017-04-19 14:28:47 +0200 | |
commit | 86addccae25e2ec4fb505ef05286e25a87c80fb5 (patch) | |
tree | 57c355a744eaaea2a1766b00d7e7dfcbb59fb774 /debian/dpdk.conf | |
parent | e771b3810e4dc12f371258e37a6a5244e326d247 (diff) |
dpdk.conf: info about unwanted effects of multiple hugepage mountpoints
Change-Id: I83d6b19ceab5fdac544b149aff78183ef8a45ff6
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Diffstat (limited to 'debian/dpdk.conf')
-rw-r--r-- | debian/dpdk.conf | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/debian/dpdk.conf b/debian/dpdk.conf index a5aea865..272565c2 100644 --- a/debian/dpdk.conf +++ b/debian/dpdk.conf @@ -36,6 +36,14 @@ # script. In that case specific mountpoints can be provided as parameters to # the DPDK library. +# Also please be aware that multiple huge page sizes and their mountpoints +# can confuse other programs as well. For example libvirt/qemu might pick one +# of the paths created for DPDKs larger pages or any such. +# It is recommended in these cases to consider configuring the respective +# applications as well to not "guess" when picking a hugepage path. +# In the libvirt/qemu case that would for example be the setting +# hugetlbfs_mount in /etc/libvirt/qemu.conf + # Hardware may support other granularities of hugepages (like 4M). But the # larger the hugepages the earlier those should be allocated. # Note: the dpdk init scripts will report warnings, but not fail if they could |