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 0916C8E79 for ; Mon, 12 Oct 2015 10:46:57 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP; 12 Oct 2015 01:46:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,671,1437462000"; d="scan'208";a="578803728" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by FMSMGA003.fm.intel.com with ESMTP; 12 Oct 2015 01:46:56 -0700 Received: from fmsmsx121.amr.corp.intel.com (10.18.125.36) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 12 Oct 2015 01:46:56 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx121.amr.corp.intel.com (10.18.125.36) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 12 Oct 2015 01:46:56 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.96]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.106]) with mapi id 14.03.0248.002; Mon, 12 Oct 2015 16:46:55 +0800 From: "Xie, Huawei" To: "Michael S. Tsirkin" Thread-Topic: [dpdk-dev] Unlinking hugepage backing file after initialiation Thread-Index: AdD6X9Ju/MtsxfWdQh2Z6wcUnply7Q== Date: Mon, 12 Oct 2015 08:46:55 +0000 Message-ID: References: <20150929161628.GA3810@redhat.com> <20150930003531-mutt-send-email-mst@redhat.com> <20151005231323-mutt-send-email-mst@redhat.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.237.220.129] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [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: Mon, 12 Oct 2015 08:46:58 -0000 On 10/5/2015 9:20 PM, Michael S. Tsirkin wrote:=0A= > But really, people should just use VFIO.=0A= Not sure if the app crashes, kernel a) unmap b) tears down IOMMU, if=0A= other app still has chance to allocate the same memory between step a=0A= and step b.=0A= Need to check whether memory are bound to huge page files after allocated.= =0A=