From: Byungchul Park <byungchul@sk.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel_team@skhynix.com, akpm@linux-foundation.org,
ying.huang@intel.com, vernhao@tencent.com,
mgorman@techsingularity.net, hughd@google.com,
willy@infradead.org, david@redhat.com, peterz@infradead.org,
luto@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, rjgolo@gmail.com
Subject: Re: [PATCH v9 1/8] x86/tlb: add APIs manipulating tlb batch's arch data
Date: Fri, 19 Apr 2024 15:06:59 +0900 [thread overview]
Message-ID: <20240419060659.GB48027@system.software.com> (raw)
In-Reply-To: <871q71ykvl.ffs@tglx>
On Fri, Apr 19, 2024 at 07:36:14AM +0200, Thomas Gleixner wrote:
> On Wed, Apr 17 2024 at 16:18, Byungchul Park wrote:
> > This is a preparation for migrc mechanism that needs to recognize
> > read-only tlb entries during migration by separating tlb batch arch data
> > into two, one is for read-only entries and the other is for writable
> > ones, and merging those two when needed.
>
> I have no idea what migrc mechanism means. Please add enough context
> into the change log so the reviewer does not have to go through loops
> and hoops to figure out what this is about.
I will add a simple description explaining 'what migrc is' at every
patch mentioning migrc, from the next spin. Thank you for the advice.
JFYI, you can see what migrc is in the following link:
https://lore.kernel.org/lkml/20240418061536.11645-1-byungchul@sk.com/
Byungchul
> Thanks,
>
> tglx
next prev parent reply other threads:[~2024-04-19 6:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 7:18 [PATCH v9 0/8] Reduce tlb and interrupt numbers over 90% by improving folio migration Byungchul Park
2024-04-17 7:18 ` [PATCH v9 1/8] x86/tlb: add APIs manipulating tlb batch's arch data Byungchul Park
2024-04-19 5:36 ` Thomas Gleixner
2024-04-19 6:06 ` Byungchul Park [this message]
2024-04-17 7:18 ` [PATCH v9 2/8] arm64: tlbflush: " Byungchul Park
2024-04-17 7:18 ` [PATCH v9 3/8] mm/rmap: recognize read-only tlb entries during batched tlb flush Byungchul Park
2024-04-17 7:18 ` [PATCH v9 4/8] x86/tlb, mm/rmap: separate arch_tlbbatch_clear() out of arch_tlbbatch_flush() Byungchul Park
2024-04-17 7:18 ` [PATCH v9 5/8] mm: separate move/undo parts from migrate_pages_batch() Byungchul Park
2024-04-17 7:18 ` [PATCH v9 6/8] mm: buddy: make room for a new variable, mgen, in struct page Byungchul Park
2024-04-17 7:18 ` [PATCH v9 7/8] mm: add folio_put_mgen() to deliver migrc's generation number to pcp or buddy Byungchul Park
2024-04-17 15:55 ` Matthew Wilcox
2024-04-18 0:20 ` Byungchul Park
2024-04-17 19:49 ` kernel test robot
2024-04-17 7:18 ` [PATCH v9 8/8] mm: defer tlb flush until the source folios at migration actually get used Byungchul Park
2024-04-17 10:33 ` [PATCH v9 0/8] Reduce tlb and interrupt numbers over 90% by improving folio migration Byungchul Park
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=20240419060659.GB48027@system.software.com \
--to=byungchul@sk.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=kernel_team@skhynix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjgolo@gmail.com \
--cc=tglx@linutronix.de \
--cc=vernhao@tencent.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).