[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230228132425.1e18d47bdc4f406220a4a409@linux-foundation.org>
Date: Tue, 28 Feb 2023 13:24:25 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Raghavendra K T <raghavendra.kt@....com>
Cc: <linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
"Mel Gorman" <mgorman@...e.de>,
"David Hildenbrand" <david@...hat.com>, <rppt@...nel.org>,
Bharata B Rao <bharata@....com>,
Disha Talreja <dishaa.talreja@....com>
Subject: Re: [PATCH V3 0/4] sched/numa: Enhance vma scanning
On Tue, 28 Feb 2023 10:20:18 +0530 Raghavendra K T <raghavendra.kt@....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.
Powered by blists - more mailing lists