linux-kernel - Re: [PATCH V3 0/4] sched/numa: Enhance vma scanning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bf81bb27-d8cb-d994-e78d-caccc55eaa26@amd.com>
Date:   Wed, 1 Mar 2023 09:46:04 +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 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.