linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yu Zhao <yuzhao@google.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Linux-MM <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Hugh Dickins <hughd@google.com>,
	"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
	 Matthew Wilcox <willy@infradead.org>,
	Vlastimil Babka <vbabka@suse.cz>, Yang Shi <shy828301@gmail.com>,
	 Zi Yan <ziy@nvidia.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	 Shuang Zhai <zhais@google.com>
Subject: Re: [PATCH 3/3] mm: don't remap clean subpages when splitting isolated thp
Date: Sun, 8 Aug 2021 11:20:30 -0600	[thread overview]
Message-ID: <CAOUHufaXA_won+fGbYx_9CBVPYcOy=RhAwP5ALwXPfNpJVwWVA@mail.gmail.com> (raw)
In-Reply-To: <20210804142729.iqtslnn3utvqgec3@box.shutemov.name>

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

On Wed, Aug 4, 2021 at 8:27 AM Kirill A. Shutemov <kirill@shutemov.name>
wrote:

> On Sat, Jul 31, 2021 at 12:39:38AM -0600, Yu Zhao wrote:
> > @@ -267,13 +308,19 @@ static bool remove_migration_pte(struct page
> *page, struct vm_area_struct *vma,
> >   * Get rid of all migration entries and replace them by
> >   * references to the indicated page.
> >   */
> > -void remove_migration_ptes(struct page *old, struct page *new, bool
> locked)
> > +void remove_migration_ptes(struct page *old, struct page *new, bool
> locked, bool unmap_clean)
> >  {
> > +     struct rmap_walk_arg rmap_walk_arg = {
> > +             .page = old,
> > +             .unmap_clean = unmap_clean,
> > +     };
> >       struct rmap_walk_control rwc = {
> >               .rmap_one = remove_migration_pte,
> > -             .arg = old,
> > +             .arg = &rmap_walk_arg,
> >       };
>
> 'old' pointer has few low always-zero bit :P
>

Will do. Thanks.

[-- Attachment #2: Type: text/html, Size: 1432 bytes --]

      reply	other threads:[~2021-08-08 18:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31  6:39 [PATCH 0/3] mm: optimize thp for reclaim and migration Yu Zhao
2021-07-31  6:39 ` [PATCH 1/3] mm: don't take lru lock when splitting isolated thp Yu Zhao
2021-07-31  6:39 ` [PATCH 2/3] mm: free zapped tail pages " Yu Zhao
2021-08-04 14:22   ` Kirill A. Shutemov
2021-08-08 17:28     ` Yu Zhao
2021-08-05  0:13   ` Yang Shi
2021-08-08 17:49     ` Yu Zhao
2021-08-11 22:25       ` Yang Shi
2021-08-11 23:12         ` Yu Zhao
2021-08-13 23:24           ` Yang Shi
2021-08-13 23:56             ` Yu Zhao
2021-08-14  0:30               ` Yang Shi
2021-08-14  1:49                 ` Yu Zhao
2021-08-14  2:34                   ` Yang Shi
2021-07-31  6:39 ` [PATCH 3/3] mm: don't remap clean subpages " Yu Zhao
2021-07-31  9:53   ` kernel test robot
2021-07-31 15:45   ` kernel test robot
2021-08-03 11:25   ` Matthew Wilcox
2021-08-03 11:36   ` Matthew Wilcox
2021-08-08 17:21     ` Yu Zhao
2021-08-04 14:27   ` Kirill A. Shutemov
2021-08-08 17:20     ` Yu Zhao [this message]

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='CAOUHufaXA_won+fGbYx_9CBVPYcOy=RhAwP5ALwXPfNpJVwWVA@mail.gmail.com' \
    --to=yuzhao@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shy828301@gmail.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    --cc=zhais@google.com \
    --cc=ziy@nvidia.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