ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Revert "test/setup: check open files limit"

Browse Source 
On multiple development systems (including mine), this results
in new error messages when running scripts/setup.sh.  This has
the potential of causing lots of questions when users upgrade
to SPDK 19.07.

I understand the desire for the error messages, but I think we have
to come up with a smarter check than just against "unlimited".

This reverts commit 0abee610f0.

Signed-off-by: Jim Harris <james.r.harris@intel.com>
Change-Id: I2854af556b67a9a4e5f686c72c4407962808f964
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/463357
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
This commit is contained in:
Jim Harris 2019-07-26 04:58:24 -07:00 committed by Darek Stojaczyk
parent 9b639aa9a4
commit 3246fd7a65
1 changed files with 0 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
scripts/setup.sh
View File

@ -374,21 +374,6 @@ function configure_linux {
exit 1
fi
CURENT_SOFT_ULIMIT=$(ulimit -n)
if [ "$CURENT_SOFT_ULIMIT" != "unlimited" ]; then
echo ""
echo "WARNING: soft ulimit for max open files is set to $CURENT_SOFT_ULIMIT."
echo "SPDK won't be able to use more than $CURENT_SOFT_ULIMIT hugepages if run as current user."
echo ""
fi
CURENT_HARD_ULIMIT=$(ulimit -Hn)
if [ "$CURENT_HARD_ULIMIT" != "unlimited" ]; then
echo ""
echo "WARNING: hard ulimit for max open files is set to $CURENT_HARD_ULIMIT."
echo "SPDK won't be able to use more than $CURENT_HARD_ULIMIT hugepages even if run as root."
echo ""
fi
if [ "$driver_name" = "vfio-pci" ]; then
if [ -n "$TARGET_USER" ]; then
for mount in $hugetlbfs_mounts; do