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
Date: Tue, 28 Feb 2023 13:24:25 -0800 [thread overview]
Message-ID: <20230228132425.1e18d47bdc4f406220a4a409@linux-foundation.org> (raw)
In-Reply-To: <cover.1677557481.git.raghavendra.kt@amd.com>
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.
next prev parent reply other threads:[~2023-02-28 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 4:50 Raghavendra K T
2023-02-28 4:50 ` [PATCH V3 1/4] sched/numa: Apply the scan delay to every new vma Raghavendra K T
2023-02-28 4:50 ` [PATCH V3 2/4] sched/numa: Enhance vma scanning logic Raghavendra K T
2023-02-28 4:50 ` [PATCH V3 3/4] sched/numa: implement access PID reset logic Raghavendra K T
2023-02-28 4:50 ` [PATCH V3 4/4] sched/numa: Use hash_32 to mix up PIDs accessing VMA Raghavendra K T
2023-02-28 21:24 ` Andrew Morton [this message]
2023-03-01 4:16 ` [PATCH V3 0/4] sched/numa: Enhance vma scanning Raghavendra K T
2023-03-01 12:32 ` Raghavendra K T
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230228132425.1e18d47bdc4f406220a4a409@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bharata@amd.com \
--cc=david@redhat.com \
--cc=dishaa.talreja@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=rppt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox