From: Sarosh Arif <sarosh.arif@emumba.com>
To: sthemmin@microsoft.com
Cc: dev@dpdk.org, Sarosh Arif <sarosh.arif@emumba.com>
Subject: [dpdk-dev] [v2 PATCH] usertools: show valid hugepage sizes if user requests an invalid hugepage size
Date: Wed, 2 Dec 2020 16:06:54 +0500 [thread overview]
Message-ID: <20201202110654.20923-1-sarosh.arif@emumba.com> (raw)
In-Reply-To: <20201130124719.23434-1-sarosh.arif@emumba.com>
If user requests a hugepage size which is not supported by the system,
currently user gets an error message saying that the requested size
is not a valid system huge page size. In addition to this if we display
the valid hugepage sizes it will be convenient for the user to request
the right size next time.
Signed-off-by: Sarosh Arif <sarosh.arif@emumba.com>
---
v2:
pass string in sys.exit() to remove pylint warning
---
usertools/dpdk-hugepages.py | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/usertools/dpdk-hugepages.py b/usertools/dpdk-hugepages.py
index 1be100ca3..09d35bf55 100755
--- a/usertools/dpdk-hugepages.py
+++ b/usertools/dpdk-hugepages.py
@@ -49,6 +49,14 @@ def get_hugepages(path):
return int(nr_hugepages.read())
return 0
+def get_valid_page_sizes(path):
+ valid_page_sizes = ""
+ hugepage_dir_path = os.path.split(path)[0]
+ hugepage_dirs = os.listdir(hugepage_dir_path)
+ for each_dir in hugepage_dirs:
+ hugepage_size = each_dir.split("-")[1]
+ valid_page_sizes = valid_page_sizes + " " + hugepage_size
+ return valid_page_sizes
def set_hugepages(path, pages):
'''Write the number of reserved huge pages'''
@@ -59,10 +67,8 @@ def set_hugepages(path, pages):
except PermissionError:
sys.exit('Permission denied: need to be root!')
except FileNotFoundError:
- filename = os.path.basename(path)
- size = filename[10:]
- sys.exit('{} is not a valid system huge page size'.format(size))
-
+ sys.exit("Invalid page size. Valid page sizes: {}".format(
+ get_valid_page_sizes(path)))
def show_numa_pages():
'''Show huge page reservations on Numa system'''
--
2.25.1
next prev parent reply other threads:[~2020-12-02 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 12:47 [dpdk-dev] [PATCH] " Sarosh Arif
2020-11-30 16:46 ` Stephen Hemminger
2020-11-30 16:47 ` Stephen Hemminger
2020-12-02 11:06 ` Sarosh Arif [this message]
2021-02-05 18:17 ` [dpdk-dev] [v2 PATCH] " Thomas Monjalon
2021-02-08 22:12 ` Stephen Hemminger
2021-02-09 11:34 ` Burakov, Anatoly
2021-02-10 6:16 ` [dpdk-dev] [v3 " Sarosh Arif
2021-02-10 17:41 ` Burakov, Anatoly
2021-02-11 8:20 ` [dpdk-dev] [v4 " Sarosh Arif
2021-02-11 16:26 ` Stephen Hemminger
2021-02-11 21:44 ` Thomas Monjalon
2021-02-11 23:16 ` Stephen Hemminger
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=20201202110654.20923-1-sarosh.arif@emumba.com \
--to=sarosh.arif@emumba.com \
--cc=dev@dpdk.org \
--cc=sthemmin@microsoft.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).