[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240724125515.6cc3bd8479ea8bcdedaa7eff@linux-foundation.org>
Date: Wed, 24 Jul 2024 12:55:15 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Zhiguo Jiang <justinjiang@...o.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org, Barry Song
<baohua@...nel.org>, David Hildenbrand <david@...hat.com>, Matthew Wilcox
<willy@...radead.org>, opensource.kernel@...o.com
Subject: Re: [PATCH v10] mm: shrink skip folio mapped by an exiting process
On Wed, 10 Jul 2024 16:36:41 +0800 Zhiguo Jiang <justinjiang@...o.com> wrote:
> The releasing process of the non-shared anonymous folio mapped solely by
> an exiting process may go through two flows: 1) the anonymous folio is
> firstly is swaped-out into swapspace and transformed into a swp_entry
> in shrink_folio_list; 2) then the swp_entry is released in the process
> exiting flow. This will result in the high cpu load of releasing a
> non-shared anonymous folio mapped solely by an exiting process.
>
> When the low system memory and the exiting process exist at the same
> time, it will be likely to happen, because the non-shared anonymous
> folio mapped solely by an exiting process may be reclaimed by
> shrink_folio_list.
>
> This patch is that shrink skips the non-shared anonymous folio solely
> mapped by an exting process and this folio is only released directly in
> the process exiting flow, which will save swap-out time and alleviate
> the load of the process exiting.
Has any testing been performed to demonstrate any benefit? If so, what
were the results?
Powered by blists - more mailing lists