[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <895b9edb-6df4-7b7c-3b4d-8628a54977cc@amd.com>
Date: Wed, 1 Mar 2023 18:02:54 +0530
From: Raghavendra K T <raghavendra.kt@....com>
To: Andrew Morton <akpm@...ux-foundation.org>
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 3/1/2023 9:46 AM, Raghavendra K T wrote:
> On 3/1/2023 2:54 AM, Andrew Morton wrote:
>> 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.
>>
>
> Thank you Andrew. Sure will do that.
>
Thanks again, Sent rebased patches,
Just to record, so that new discussion can happen in new posting
https://lore.kernel.org/lkml/cover.1677672277.git.raghavendra.kt@amd.com/T/#t
Powered by blists - more mailing lists