What I heard is the following: A multi-process DPDK application, working either
in master-worker or master-slave fashion, can potentially benefit by keeping
the backing files in hugetlbfs. However, it is does not work today as the pages
are cleaned and added back when the application restarts. On the other hand,
for a single process application there is actually no benefit keeping the pages
around.
Therefore, I was wondering if we can make this configurable by passing a
command line argument that will either unlink or keep the backing files.
--
- Thanks
char * (*shesha) (uint64_t cache, uint8_t F00D)
{ return 0x0000C0DE; }
From: "Michael S. Tsirkin" <mst at redhat.com<mailto:m...@redhat.com>>
Date: Tuesday, September 29, 2015 at 2:35 PM
To: Cisco Employee <shesha at cisco.com<mailto:shesha at cisco.com>>
Cc: "Xie, Huawei" <huawei.xie at intel.com<mailto:huawei.xie at intel.com>>,
"dev at dpdk.org<mailto:dev at dpdk.org>" <dev at dpdk.org<mailto:dev at
dpdk.org>>
Subject: Re: [dpdk-dev] Unlinking hugepage backing file after initialiation
On Tue, Sep 29, 2015 at 05:50:00PM +0000, shesha Sreenivasamurthy (shesha)
wrote:
Sure. Then, is there any real reason why the backing files should not be
unlinked ?
AFAIK qemu unlinks them already.
--
MST
