On 10/5/2015 9:20 PM, Michael S. Tsirkin wrote:
> But really, people should just use VFIO.
Not sure if the app crashes, kernel a) unmap b) tears down IOMMU, if
other app still has chance to allocate the same memory between step a
and step b.
Need to check whether memory are bound to huge page files
On Mon, Oct 05, 2015 at 01:08:52PM +, Xie, Huawei wrote:
> On 9/30/2015 5:36 AM, Michael S. Tsirkin wrote:
> > On Tue, Sep 29, 2015 at 05:50:00PM +, shesha Sreenivasamurthy (shesha)
> > wrote:
> >> Sure. Then, is there any real reason why the backing files should not be
> >> unlinked ?
> >
On 9/30/2015 5:36 AM, Michael S. Tsirkin wrote:
> On Tue, Sep 29, 2015 at 05:50:00PM +, shesha Sreenivasamurthy (shesha)
> wrote:
>> Sure. Then, is there any real reason why the backing files should not be
>> unlinked ?
> AFAIK qemu unlinks them already.
Sorry, i didn't make it clear. Let us t
Sent: Wednesday, September 30, 2015 10:44 PM
> To: dev at dpdk.org<mailto:dev at dpdk.org>
> Cc: Michael S. Tsirkin
> Subject: Re: [dpdk-dev] Unlinking hugepage backing file after initialiation
> What I heard is the following: A multi-process DPDK application, working
> either
Date: Wednesday, September 30, 2015 at 2:53 PM
To: Cisco Employee mailto:shesha at cisco.com>>, "dev at
dpdk.org<mailto:dev at dpdk.org>" mailto:dev at dpdk.org>>
Cc: "Michael S. Tsirkin" mailto:mst at redhat.com>>
Subject: RE: [dpdk-dev] Unlinkin
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of shesha
> Sreenivasamurthy (shesha)
> Sent: Wednesday, September 30, 2015 10:44 PM
> To: dev at dpdk.org
> Cc: Michael S. Tsirkin
> Subject: Re: [dpdk-dev] Unlinking hugepage backing fil
.org<mailto: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 +, 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
On Tue, Sep 29, 2015 at 05:50:00PM +, 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
On Tue, Sep 29, 2015 at 03:48:08PM +, shesha Sreenivasamurthy (shesha)
wrote:
> If huge pages are allocated for the guest and if the guest crashes there may
> be
> a chance that the new guest may not be able to get huge pages again as some
> other guest or process on the host used it. But I a
: Cisco Employee mailto:shesha at cisco.com>>
Cc: "Xie, Huawei" mailto:huawei.xie at intel.com>>,
"dev at dpdk.org<mailto: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 0
ay, September 29, 2015 at 8:15 AM
To: Cisco Employee mailto:shesha at cisco.com>>
Cc: "dev at dpdk.org<mailto:dev at dpdk.org>" mailto:dev at
dpdk.org>>, "ms >> Michael S. Tsirkin" mailto:mst at
redhat.com>>
Subject: Re: [dpdk-dev] Unlinking hugepage ba
On 9/29/2015 10:38 AM, Xie, Huawei wrote:
> On 9/29/2015 8:04 AM, shesha Sreenivasamurthy (shesha) wrote:
>> 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 initia
y (shesha)
> Sent: Tuesday, September 29, 2015 1:04 AM
> To: dev at dpdk.org<mailto:dev at dpdk.org>
> Subject: [dpdk-dev] Unlinking hugepage backing file after initialiation
>
> Hello,
> As of DPDK2.1, backing files are created in hugetablefs during mapping (in
> eal_me
v at dpdk.org
> > Subject: [dpdk-dev] Unlinking hugepage backing file after initialiation
> >
> > 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
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of shesha
> Sreenivasamurthy (shesha)
> Sent: Tuesday, September 29, 2015 1:04 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] Unlinking hugepage backing file after initialiation
>
>
On 9/29/2015 8:04 AM, shesha Sreenivasamurthy (shesha) wrote:
> 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 applic
Cisco Employee mailto:she...@cisco.com>>
Date: Monday, September 28, 2015 at 5:04 PM
To: "dev at dpdk.org<mailto:dev at dpdk.org>" mailto:dev at
dpdk.org>>
Subject: [dpdk-dev] Unlinking hugepage backing file after initialiation
Hello,
As of DPDK2.1, backing files are created
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
18 matches
Mail list logo
