Document dpdk tool for cleaning up huge pages#65
Document dpdk tool for cleaning up huge pages#65koolzz merged 4 commits intosdnfv:developfrom rskennedy:patch-1
Conversation
Sometimes using `sudo rm -rf /mnt/huge/*` doesn't work while the dpdk setup script can fix the problem. This was posted in the slack but it would be good to have documented.
| - In this case, either kill them manually by hitting Ctrl+C or run `sudo pkill NF_NAME` for every NF that you have ran. | ||
| - The manager and NFs are not running, but something crashed without freeing hugepages. | ||
| - To fix this, please run `sudo rm -rf /mnt/huge/*` to remove all files that contain hugepage data. | ||
| - An alternative method is to use the dpdk provided tools (the following may have changed since DPDK v18.11): Run `cd dpdk/usertools; sudo ./dpdk-setup.sh` then select "remove hugepage mappings" from the list of options. Then run `$ONVM_HOME/scripts/setup_environment.sh` to remount hugepages. |
There was a problem hiding this comment.
There is no need to run the dpdk script with sudo
There was a problem hiding this comment.
I've had a lot of success with the dpdk/usertools/dpdk-setup.sh script, when no hugepages are found I just use the Setup hugepage mappings for NUMA systems option and it almost always fixes the hugepages. On quick investigation our setup_environment.sh script isn't doing the same steps that the dpdk script does for allocating huge pages, maybe its just outdated?.
I think this pr should just fix our scripts instead of saying to run the dpdk script, or alternatively we could just use the dpdk script and instruct people to install dpdk step by step(not so nice as it requires more effort when installing)
|
should our setup script be directly calling the dpdk version instead of trying to reimplement? Is it possible to call that script in a programmatic way, or does it expect user input? |
|
@twood02 Some of it relies on user input so I'm not sure how things like adding huge pages would behave if we want to do it programmatically. |
|
I suggest we add a few lines on how dpdk installation works (as a workaround when using the onvm install script that doesn't work). mTCP does this in a nice way https://github.com/mtcp-stack/mtcp#dpdk-version |
|
@onvm let's see if you work here! |
CI MessageYour results will arrive shortly |
CI MessageError: ERROR: Failed to analyze results from nimbnode30 Linter Failedexamples/aes_decrypt/aes.c:523: If an else has a brace on one side, it should have it on both [readability/braces] [5] |
|
Tested setting up fresh install using the |
koolzz
left a comment
koolzz
left a comment
There was a problem hiding this comment.
Nice, I changed step 22 to 1024 hugepages, will merge soon.
koolzz
dismissed
twood02’s stale review
Resolved in the install script update PR
5 participants
Sometimes using
sudo rm -rf /mnt/huge/*doesn't work while the dpdk setup script can fix the problem. This was posted in the slack but it would be good to have documented.Style nits welcome!
Reviewers: @twood02 @dreidenbaugh