From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id B078A1288 for ; Mon, 15 Jun 2015 10:46:54 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP; 15 Jun 2015 01:46:53 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,617,1427785200"; d="scan'208,217";a="508412323" Received: from kmsmsx151.gar.corp.intel.com ([172.21.73.86]) by FMSMGA003.fm.intel.com with ESMTP; 15 Jun 2015 01:46:52 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by KMSMSX151.gar.corp.intel.com (172.21.73.86) with Microsoft SMTP Server (TLS) id 14.3.224.2; Mon, 15 Jun 2015 16:46:51 +0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.129]) by shsmsx102.ccr.corp.intel.com ([169.254.2.165]) with mapi id 14.03.0224.002; Mon, 15 Jun 2015 16:46:50 +0800 From: "Du, Fan" To: "dev@dpdk.org" Thread-Topic: huge page didn't get freed when dpdk-app exit(or killed) Thread-Index: AdCnR21sDSngYu4KSu2rzpusuQQMWA== Date: Mon, 15 Jun 2015 08:46:49 +0000 Message-ID: <5A90DA2E42F8AE43BC4A093BF0678848E6B959@SHSMSX104.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] huge page didn't get freed when dpdk-app exit(or killed) X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2015 08:46:55 -0000 Hi, I play OpenvSwitch dpdk, when ovs-vswitchd got killed, it won't free up any= allocated huge pages, shown by below: # tail /proc/meminfo HardwareCorrupted: 0 kB AnonHugePages: 106496 kB HugePages_Total: 8 HugePages_Free: 6 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 1048576 kB DPDK setup hugepage by below steps, in function rte_eal_hugepage_init * 1. map N huge pages in separate files in hugetlbfs * 2. find associated physical addr * 3. find associated NUMA socket ID * 4. sort all huge pages by physical address * 5. remap these N huge pages in the correct order * 6. unmap the first mapping * 7. fill memsegs in configuration with contiguous zones So my env shows below when allocated 2G huge pages. # ls /dev/hugepages/ libvirt rtemap_4 rtemap_7 So in scenario where dpdk app is stop, but hugepage will be used by other n= on-dpdk app, Would current dpdk huge page behavior(not freed huge page when app exited) = be a problem? I found out this patch: http://dpdk.org/dev/patchwork/patch/993/ tries to p= rovide an interface, It didn't get merged with additional implementation modification. Then is there any follow ups for this issue? A pointer will be much appreci= ated! Thanks!