Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38;
Date:   Tue, 19 Sep 2023 11:28:30 +0200
From:   Peter Zijlstra <peterz@infradead.org>
To:     Raghavendra K T <raghavendra.kt@amd.com>
Cc:     linux-kernel@vger.kernel.org, linux-mm@kvack.org,
        Ingo Molnar <mingo@redhat.com>, Mel Gorman <mgorman@suse.de>,
        Andrew Morton <akpm@linux-foundation.org>,
        David Hildenbrand <david@redhat.com>, rppt@kernel.org,
        Juri Lelli <juri.lelli@redhat.com>,
        Vincent Guittot <vincent.guittot@linaro.org>,
        Bharata B Rao <bharata@amd.com>,
        Aithal Srikanth <sraithal@amd.com>,
        kernel test robot <oliver.sang@intel.com>,
        Sapkal Swapnil <Swapnil.Sapkal@amd.com>,
        K Prateek Nayak <kprateek.nayak@amd.com>
Subject: Re: [RFC PATCH V1 0/6] sched/numa: Enhance disjoint VMA scanning
Message-ID: <20230919092830.GF21729@noisy.programming.kicks-ass.net>
References: <cover.1693287931.git.raghavendra.kt@amd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cover.1693287931.git.raghavendra.kt@amd.com>
Precedence: bulk

On Tue, Aug 29, 2023 at 11:36:08AM +0530, Raghavendra K T wrote:

> Peter Zijlstra (1):
>   sched/numa: Increase tasks' access history
> 
> Raghavendra K T (5):
>   sched/numa: Move up the access pid reset logic
>   sched/numa: Add disjoint vma unconditional scan logic
>   sched/numa: Remove unconditional scan logic using mm numa_scan_seq
>   sched/numa: Allow recently accessed VMAs to be scanned
>   sched/numa: Allow scanning of shared VMAs
> 
>  include/linux/mm.h       |  12 +++--
>  include/linux/mm_types.h |   5 +-
>  kernel/sched/fair.c      | 109 ++++++++++++++++++++++++++++++++-------
>  3 files changed, 102 insertions(+), 24 deletions(-)

So I don't immediately see anything horrible with this. Mel, do you have
a few cycles to go over this as well?