[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8dEv/YeZt+TRSlv@casper.infradead.org>
Date: Wed, 18 Jan 2023 01:00:47 +0000
From: Matthew Wilcox <willy@...radead.org>
To: "T.J. Alumbaugh" <talumbau@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-mm@...gle.com
Subject: Re: [PATCH mm-unstable v1 1/7] mm: multi-gen LRU: section for
working set protection
On Wed, Jan 18, 2023 at 12:18:21AM +0000, T.J. Alumbaugh wrote:
> +++ b/mm/vmscan.c
> @@ -4475,6 +4475,10 @@ static bool try_to_inc_max_seq(struct lruvec *lruvec, unsigned long max_seq,
> return true;
> }
>
> +/******************************************************************************
> + * working set protection
> + ******************************************************************************/
> +
> static bool lruvec_is_sizable(struct lruvec *lruvec, struct scan_control *sc)
We don't usually do this. Why do you want to?
Powered by blists - more mailing lists