From: Raghavendra K T <raghavendra.kt@amd.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Ingo Molnar <mingo@redhat.com>, Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
rppt@kernel.org, Bharata B Rao <bharata@amd.com>,
Disha Talreja <dishaa.talreja@amd.com>
Subject: Re: [PATCH V2 2/3] sched/numa: Enhance vma scanning logic
Date: Mon, 27 Feb 2023 15:42:46 +0530 [thread overview]
Message-ID: <3a9269bf-0d1c-59b4-f80f-afbbdf9c45b4@amd.com> (raw)
In-Reply-To: <Y/yAmDj6tQVfOdqK@hirez.programming.kicks-ass.net>
On 2/27/2023 3:36 PM, Peter Zijlstra wrote:
> On Mon, Feb 27, 2023 at 12:10:41PM +0530, Raghavendra K T wrote:
>> In summary: I do see that access to VMAs from disjoint sets is not fully
>> fair, But on the other hand it is not very bad too. There is definitely
>> some scope or possibility to explore/improve fairness in this area
>> further.
>
> Ok, might be good to summarize some of this in a comment near here, so
> that readers are aware of the caveat of this code.
>
Sure will do.
>> PS: I have also tested above applying V3 patch (which incorporates your
>> suggestions), have not seen much deviation in observation with patch.
>
> I'll see if I can find it in this dumpester fire I call inbox :-)
Sorry I wasn't clear there.. Still in inbox and am about to post.. It
was a heads up.
next prev parent reply other threads:[~2023-02-27 10:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 8:02 [PATCH V2 0/3] sched/numa: Enhance vma scanning Raghavendra K T
2023-02-01 8:02 ` [PATCH V2 1/3] sched/numa: Apply the scan delay to every vma instead of tasks Raghavendra K T
2023-02-03 10:24 ` Peter Zijlstra
2023-02-04 17:19 ` Raghavendra K T
2023-02-01 8:02 ` [PATCH V2 2/3] sched/numa: Enhance vma scanning logic Raghavendra K T
2023-02-03 11:15 ` Peter Zijlstra
2023-02-03 11:27 ` Peter Zijlstra
2023-02-04 18:18 ` Raghavendra K T
2023-02-04 18:14 ` Raghavendra K T
2023-02-07 6:41 ` Raghavendra K T
2023-02-27 6:40 ` Raghavendra K T
2023-02-27 10:06 ` Peter Zijlstra
2023-02-27 10:12 ` Raghavendra K T [this message]
2023-02-28 4:59 ` Raghavendra K T
2023-02-01 8:02 ` [PATCH V2 3/3] sched/numa: Reset the accessing PID information periodically Raghavendra K T
2023-02-03 11:35 ` Peter Zijlstra
2023-02-04 18: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=3a9269bf-0d1c-59b4-f80f-afbbdf9c45b4@amd.com \
--to=raghavendra.kt@amd.com \
--cc=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=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