From 2e1c5a722da9ce16ab8b327547d042a81148370a Mon Sep 17 00:00:00 2001 From: Jim Harris Date: Wed, 22 Mar 2023 06:08:11 +0000 Subject: [PATCH] dpdk_mem_info.py: handle spaces in mempool names DPDK is OK with spaces in mempool names. SPDK has never done it, but latest OCF code uses a name with a space that gets used as a mempool name. The dpdk_mem_info.py script was parsing mempool information assuming there were no spaces in the name. So this patch fixes it. Note: I created a dummy memzone with a space in its name, and confirmed that works correctly. So only mempool names needed to be fixed. Signed-off-by: Jim Harris Change-Id: I76d4e6e94852dd697b4be187e6ee625db867867a Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/17316 Reviewed-by: Konrad Sztyber Reviewed-by: Ben Walker Reviewed-by: Amir Haroush Tested-by: SPDK CI Jenkins --- scripts/dpdk_mem_info.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/scripts/dpdk_mem_info.py b/scripts/dpdk_mem_info.py index 52449582b..1532d2546 100755 --- a/scripts/dpdk_mem_info.py +++ b/scripts/dpdk_mem_info.py @@ -265,11 +265,10 @@ def parse_segment(line): def parse_mempool_name(line): - trash, info = line.split() name, addr = line.split('@') name = name.replace("<", "") name = name.replace(">", "") - trash, name = name.split() + trash, sep, name = name.partition(' ') return name