From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by dpdk.org (Postfix) with ESMTP id 149BC1396 for ; Tue, 29 Sep 2015 02:04:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2444; q=dns/txt; s=iport; t=1443485050; x=1444694650; h=from:to:subject:date:message-id:mime-version; bh=lmH0tQwFj40TTF5NzPPFllkfoU4jeX/JEB4DfONRAKI=; b=kC1nAcaDaCnZA8AgZ7iuO9Wi7JNLiOBkchexOIM8P8ZlpqGMKDofhW/H nsfmeGw6ET4QgTZOui0sYpvKi2hOFtvwO5tCkUHsEQ81N4kSH/ljJyx6v SghLBS6V4766fSfYOZvoYopz7eS+27LNQQTWGqSsI5z4BLV+WMw8T7oOJ s=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AHBQCL1AlW/40NJK1dgldNgUO9R4lIOhIBAQEBAQEBfwuEK4ELAQwBcycEiEGnIqREAQsBH5UwBZVwAXeMF5s/KAM4hAGJDYEFAQEB X-IronPort-AV: E=Sophos;i="5.17,605,1437436800"; d="scan'208,217";a="192402323" Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-5.cisco.com with ESMTP; 29 Sep 2015 00:04:08 +0000 Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t8T048k6024384 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Tue, 29 Sep 2015 00:04:08 GMT Received: from xch-aln-009.cisco.com (173.36.7.19) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 28 Sep 2015 19:04:08 -0500 Received: from xhc-rcd-x08.cisco.com (173.37.183.82) by xch-aln-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Mon, 28 Sep 2015 19:04:08 -0500 Received: from xmb-aln-x03.cisco.com ([169.254.6.63]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0248.002; Mon, 28 Sep 2015 19:04:08 -0500 From: "shesha Sreenivasamurthy (shesha)" To: "dev@dpdk.org" Thread-Topic: Unlinking hugepage backing file after initialiation Thread-Index: AQHQ+kpckJG1vBipX0G0rq8U7ayRsA== Date: Tue, 29 Sep 2015 00:04:07 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [64.101.220.158] 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] Unlinking hugepage backing file after initialiation 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: Tue, 29 Sep 2015 00:04:10 -0000 Hello, As of DPDK2.1, backing files are created in hugetablefs during mapping (in = eal_memory.c::rte_eal_hugepage_init()) and these files are not cleaned up (= unlinked) after initialization (mmap-ing). This means, when the application= crashes or stopped, the memory is still consumed. Therefore, is there any = reason not to unlink backing files after initialization ? If no, I will sen= d a patch for the change. -- - Thanks char * (*shesha) (uint64_t cache, uint8_t F00D) { return 0x0000C0DE; }