From: Nadav Amit <nadav.amit@gmail.com>
To: Peter Xu <peterx@redhat.com>
Cc: Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Huang Ying <ying.huang@intel.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Hugh Dickins <hughd@google.com>,
David Hildenbrand <david@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH RFC 0/4] mm: Remember young bit for migration entries
Date: Fri, 29 Jul 2022 10:07:02 -0700 [thread overview]
Message-ID: <6C0B267E-E36D-4014-8308-B948247D7FED@gmail.com> (raw)
In-Reply-To: <20220729014041.21292-1-peterx@redhat.com>
On Jul 28, 2022, at 6:40 PM, Peter Xu <peterx@redhat.com> wrote:
> [Marking as RFC; only x86 is supported for now, plan to add a few more
> archs when there's a formal version]
>
> Problem
> =======
>
> When migrate a page, right now we always mark the migrated page as old.
> The reason could be that we don't really know whether the page is hot or
> cold, so we could have taken it a default negative assuming that's safer.
Looks good to me.
I just wonder whether the order of the patches should be different. I always
understood that separating the “enabling” patch from the others is not a
good practice, since it complicates bisection. I guess it is more of a minor
issue for such a small patch-set…
next prev parent reply other threads:[~2022-07-29 17:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 1:40 Peter Xu
2022-07-29 1:40 ` [PATCH RFC 1/4] mm/swap: Add swp_offset_pfn() to fetch PFN from swap entry Peter Xu
2022-08-01 3:13 ` Huang, Ying
2022-08-01 22:29 ` Peter Xu
2022-08-02 1:22 ` Huang, Ying
2022-07-29 1:40 ` [PATCH RFC 2/4] mm: Remember young bit for page migrations Peter Xu
2022-07-29 1:40 ` [PATCH RFC 3/4] mm/x86: Use SWP_TYPE_BITS in 3-level swap macros Peter Xu
2022-07-29 1:40 ` [PATCH RFC 4/4] mm/x86: Define __ARCH_SWP_OFFSET_BITS Peter Xu
2022-07-29 17:07 ` Nadav Amit [this message]
2022-07-29 22:43 ` [PATCH RFC 0/4] mm: Remember young bit for migration entries Peter Xu
2022-08-01 3:20 ` Huang, Ying
2022-08-01 5:33 ` Huang, Ying
2022-08-01 22:25 ` Peter Xu
2022-08-01 8:21 ` David Hildenbrand
2022-08-01 22:35 ` Peter Xu
2022-08-02 12:06 ` David Hildenbrand
2022-08-02 20:14 ` Peter Xu
2022-08-02 20:23 ` David Hildenbrand
2022-08-02 20:35 ` Peter Xu
2022-08-02 20:59 ` David Hildenbrand
2022-08-02 22:15 ` Peter Xu
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=6C0B267E-E36D-4014-8308-B948247D7FED@gmail.com \
--to=nadav.amit@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=vbabka@suse.cz \
--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