Bug 1072 - hugetlbfs file descriptor not closed after memery created
Summary: hugetlbfs file descriptor not closed after memery created
Status: UNCONFIRMED
Alias: None
Product: DPDK
Classification: Unclassified
Component: core (show other bugs)
Version: 21.11
Hardware: All Linux
: Normal normal
Target Milestone: ---
Assignee: dev
URL:
Depends on:
Blocks:
 
Reported: 2022-09-01 09:30 CEST by zero
Modified: 2022-09-01 09:50 CEST (History)
0 users



Attachments

Description zero 2022-09-01 09:30:29 CEST

    
Comment 1 zero 2022-09-01 09:50:02 CEST
after my app started ,use lsof -p xxx -n,it gives me the different result.
in 18.01,it only in the memery:
    ad_appd 29465 root  mem-R     REG               0,39   2097152    672832 /dev/hugepages/rtemap_249

however in 21.11,it has two lines
    ad_appd 29465 root  mem-R     REG               0,39   2097152    672833 /dev/hugepages/rtemap_250
    ad_appd 29465 root  293uR     REG               0,39   2097152    672833 /dev/hugepages/rtemap_250

and it cost an open file in ulimit -n
when I increase the hugepages,it would return an error:
    EAL: rte_mem_virt2phy(): cannot open /proc/self/pagemap: Too many open files

I just read it that we can use the eal params --single-file-segments and --in-memery to fix the problem,but I still wunder if this is a bug or if it's a new feature in 21.11, and if I use --single-file-segments and --in-memery to solve the problem, would it cause other problem,like performance decrease.

 thanks.

Note You need to log in before you can comment on or make changes to this bug.