Message-ID: <278ec047-4c5d-ab71-de36-094dbed4067c@redhat.com>
Date:   Tue, 7 Mar 2023 11:10:23 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.8.0
Subject: Re: THP backed thread stacks
Content-Language: en-US
To:     Mike Kravetz <mike.kravetz@oracle.com>, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org
References: <20230306235730.GA31451@monkey>
Cc:     Rik van Riel <riel@surriel.com>
From:   David Hildenbrand <david@redhat.com>
Organization: Red Hat
In-Reply-To: <20230306235730.GA31451@monkey>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 07.03.23 00:57, Mike Kravetz wrote:
> One of our product teams recently experienced 'memory bloat' in their
> environment.  The application in this environment is the JVM which
> creates hundreds of threads.  Threads are ultimately created via
> pthread_create which also creates the thread stacks.  pthread attributes
> are modified so that stacks are 2MB in size.  It just so happens that
> due to allocation patterns, all their stacks are at 2MB boundaries.

Is this also related to a recent change, where we try to always align at 
PMD boundaries now, such that this gets more likely?

commit f35b5d7d676e59e401690b678cd3cfec5e785c23
Author: Rik van Riel <riel@surriel.com>
Date:   Tue Aug 9 14:24:57 2022 -0400

     mm: align larger anonymous mappings on THP boundaries


As a side note, I even heard of complains about memory bloat when 
switching from 4k -> 64k page size with many threads ...

-- 
Thanks,

David / dhildenb