Date:   Tue, 28 Feb 2023 13:24:25 -0800
From:   Andrew Morton <akpm@linux-foundation.org>
To:     Raghavendra K T <raghavendra.kt@amd.com>
Cc:     <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
        Ingo Molnar <mingo@redhat.com>,
        Peter Zijlstra <peterz@infradead.org>,
        "Mel Gorman" <mgorman@suse.de>,
        "David Hildenbrand" <david@redhat.com>, <rppt@kernel.org>,
        Bharata B Rao <bharata@amd.com>,
        Disha Talreja <dishaa.talreja@amd.com>
Subject: Re: [PATCH V3 0/4] sched/numa: Enhance vma scanning
Message-Id: <20230228132425.1e18d47bdc4f406220a4a409@linux-foundation.org>
In-Reply-To: <cover.1677557481.git.raghavendra.kt@amd.com>
References: <cover.1677557481.git.raghavendra.kt@amd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 28 Feb 2023 10:20:18 +0530 Raghavendra K T <raghavendra.kt@amd.com> wrote:

>  The patchset proposes one of the enhancements to numa vma scanning
> suggested by Mel. This is continuation of [3]. 
> 
> ...
> 
>  include/linux/mm.h       | 30 +++++++++++++++++++++
>  include/linux/mm_types.h |  9 +++++++
>  kernel/fork.c            |  2 ++
>  kernel/sched/fair.c      | 57 ++++++++++++++++++++++++++++++++++++++++
>  mm/memory.c              |  3 +++

It's unclear (to me) which tree would normally carry these.

But there are significant textual conflicts with the "Per-VMA locks"
patchset, and there might be functional issues as well.  So mm.git
would be the better choice.

Please can you redo and retest against tomorrow's mm-unstable branch
(git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm)?  Hopefully the
sched developers can take a look and provide feedback.

Thanks.