On Sun, Oct 16, 2011 at 8:33 PM, Andi Kleen wrote:
> On Sun, Oct 16, 2011 at 12:38:16PM +0200, Richard Guenther wrote:
>> On Sun, Oct 16, 2011 at 7:30 AM, Andi Kleen wrote:
>> > Andi Kleen writes:
>> >
>> >> From: Andi Kleen
>> >>
>> >> Use the Linux MADV_DONTNEED call to unmap free pages in th
On Sun, Oct 16, 2011 at 12:38:16PM +0200, Richard Guenther wrote:
> On Sun, Oct 16, 2011 at 7:30 AM, Andi Kleen wrote:
> > Andi Kleen writes:
> >
> >> From: Andi Kleen
> >>
> >> Use the Linux MADV_DONTNEED call to unmap free pages in the garbage
> >> collector.Then keep the unmapped pages in the
On Sun, Oct 16, 2011 at 7:30 AM, Andi Kleen wrote:
> Andi Kleen writes:
>
>> From: Andi Kleen
>>
>> Use the Linux MADV_DONTNEED call to unmap free pages in the garbage
>> collector.Then keep the unmapped pages in the free list. This avoid
>> excessive memory fragmentation on large LTO bulds, whi
Andi Kleen writes:
> From: Andi Kleen
>
> Use the Linux MADV_DONTNEED call to unmap free pages in the garbage
> collector.Then keep the unmapped pages in the free list. This avoid
> excessive memory fragmentation on large LTO bulds, which can lead
> to gcc bumping into the Linux vm_max_map limit
> So can we move the param patch back as a possible followup?
I can drop it, however it will still mean fragmentation on any
non Linux (or rather non MADV_DONTNEED) hosts.
-Andi
On Mon, Oct 10, 2011 at 4:04 PM, Andi Kleen wrote:
>> Shouldn't we prefer still "mapped" pages when allocating? Thus, keep
>> the freepages list "sorted"?
>
> Possibly. I can look at it in a followup if you want.
> I would prefer to not complicate this patch too much.
>
>>
>> With the new params
> Shouldn't we prefer still "mapped" pages when allocating? Thus, keep
> the freepages list "sorted"?
Possibly. I can look at it in a followup if you want.
I would prefer to not complicate this patch too much.
>
> With the new params to call release_pages less, how does this
> interact with us
On Mon, Oct 10, 2011 at 01:11:13PM +0200, Richard Guenther wrote:
> > I don't see why. MADV_DONTNEED isn't perfect, what it does (on Linux)
> > is that it zaps the whole page range, which essentially brings it into
> > the exact same state as immediately after mmap. Any touch of the
> > pages wil
On Mon, Oct 10, 2011 at 12:45 PM, Jakub Jelinek wrote:
> On Mon, Oct 10, 2011 at 12:25:15PM +0200, Richard Guenther wrote:
>> On Sun, Oct 9, 2011 at 9:55 PM, Andi Kleen wrote:
>> > From: Andi Kleen
>> >
>> > Use the Linux MADV_DONTNEED call to unmap free pages in the garbage
>> > collector.Then
On Mon, Oct 10, 2011 at 12:25:15PM +0200, Richard Guenther wrote:
> On Sun, Oct 9, 2011 at 9:55 PM, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > Use the Linux MADV_DONTNEED call to unmap free pages in the garbage
> > collector.Then keep the unmapped pages in the free list. This avoid
> > excess
On Sun, Oct 9, 2011 at 9:55 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> Use the Linux MADV_DONTNEED call to unmap free pages in the garbage
> collector.Then keep the unmapped pages in the free list. This avoid
> excessive memory fragmentation on large LTO bulds, which can lead
> to gcc bumping i
From: Andi Kleen
Use the Linux MADV_DONTNEED call to unmap free pages in the garbage
collector.Then keep the unmapped pages in the free list. This avoid
excessive memory fragmentation on large LTO bulds, which can lead
to gcc bumping into the Linux vm_max_map limit per process.
Based on a idea f
12 matches
Mail list logo
