From: "David Wang" <00107082@163.com>
To: "Suren Baghdasaryan" <surenb@google.com>
Cc: yuzhao@google.com, kent.overstreet@linux.dev,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/codetag: swap tags when migrate pages
Date: Sat, 30 Nov 2024 07:43:38 +0800 (CST) [thread overview]
Message-ID: <3a513838.11a.1937a4f0215.Coremail.00107082@163.com> (raw)
In-Reply-To: <CAJuCfpGxU8u4X0x1n3Sen206Xpi1ubBK2gyCgYinPV_NFFJNPw@mail.gmail.com>
At 2024-11-30 06:59:26, "Suren Baghdasaryan" <surenb@google.com> wrote:
>On Thu, Nov 28, 2024 at 6:52 PM David Wang <00107082@163.com> wrote:
>>
>> Current solution to adjust codetag references during page migration is
>> done in 3 steps:
>> 1. sets the codetag reference of the old page as empty (not pointing
>> to any codetag);
>> 2. subtracts counters of the new page to compensate for its own allocation;
>> 3. sets codetag reference of the new page to point to the codetag of
>> the old page.
>> This does not work if CONFIG_MEM_ALLOC_PROFILING_DEBUG=n because
>> set_codetag_empty() becomes NOOP. Instead, let's simply swap codetag
>> references so that the new page is referencing the old codetag and the
>> old page is referencing the new codetag. This way accounting stays
>> valid and the logic makes more sense.
>>
>> Fixes: e0a955bf7f61 ("mm/codetag: add pgalloc_tag_copy()")
>> Signed-off-by: David Wang <00107082@163.com>
>> Closes: https://lore.kernel.org/lkml/20241124074318.399027-1-00107082@163.com/
>> Acked-by: Suren Baghdasaryan <surenb@google.com>
>> Suggested-by: Suren Baghdasaryan <surenb@google.com>
>
>Thanks! This looks fine to me but IIRC I did not Ack this patch
Sorry, I am kind of new to the kernel development process, still catching up.
>before. In the future please do not add Acked-by until you get an
>explicit Ack. That said,
Roger that~
I was wondering when "Acked-by~ or "Rreviewd-by" were added in other commits. Now I understand,
I am not supposed to do that.
Thanks
David
>
next prev parent reply other threads:[~2024-11-29 23:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 10:26 [PATCH] " David Wang
2024-11-28 19:53 ` Suren Baghdasaryan
2024-11-28 19:54 ` Suren Baghdasaryan
2024-11-29 1:13 ` David Wang
2024-11-29 2:52 ` [PATCH v2] " David Wang
2024-11-29 22:59 ` Suren Baghdasaryan
2024-11-29 23:43 ` David Wang [this message]
2024-12-02 22:19 ` Yu Zhao
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=3a513838.11a.1937a4f0215.Coremail.00107082@163.com \
--to=00107082@163.com \
--cc=akpm@linux-foundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--cc=yuzhao@google.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