From:   David Laight <David.Laight@ACULAB.COM>
To:     'Matthew Wilcox' <willy@infradead.org>,
        Mike Kravetz <mike.kravetz@oracle.com>
CC:     "linux-mm@kvack.org" <linux-mm@kvack.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: THP backed thread stacks
Thread-Topic: THP backed thread stacks
Thread-Index: AQHZWPlZJwMTNLTeV0WLE6c5qQ1d3K8AfxPA
Date:   Sat, 18 Mar 2023 12:58:20 +0000
Message-ID: <9725accc24aa4d76b01cdc9b210d12d4@AcuMS.aculab.com>
References: <20230306235730.GA31451@monkey>
 <ZBSo+mLUOsKvy3rC@casper.infradead.org>
In-Reply-To: <ZBSo+mLUOsKvy3rC@casper.infradead.org>
Accept-Language: en-GB, en-US
MIME-Version: 1.0
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Precedence: bulk

From: Matthew Wilcox
> Sent: 17 March 2023 17:53
...
> My understanding is that for a normal app (like, say, 'cat'), we'll
> allow up to an 8MB stack, but we only create a VMA that is 4kB in size
> and set the VM_GROWSDOWN flag on it (to allow it to magically grow).
> Therefore we won't create a 2MB page because the VMA is too small.

Is there anyway that glibc (or anything else) could request that
for a thread stack?

It would make the process 'memory size' reported by ps/top
much more meaningful for programs with threads.
I've noticed some (what should be) small programs having a
size (rss?) of 277m.
I'm sure a lot of it is thread stack.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)