From: Mel Gorman <mgorman@suse.de>
To: Yang Shi <shy828301@gmail.com>
Cc: kirill.shutemov@linux.intel.com, ziy@nvidia.com,
ying.huang@intel.com, mhocko@suse.com, hughd@google.com,
gerald.schaefer@linux.ibm.com, hca@linux.ibm.com,
gor@linux.ibm.com, borntraeger@de.ibm.com,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [v3 PATCH 1/7] mm: memory: add orig_pmd to struct vm_fault
Date: Wed, 19 May 2021 09:13:12 +0100 [thread overview]
Message-ID: <20210519081312.GC3672@suse.de> (raw)
In-Reply-To: <20210518200801.7413-2-shy828301@gmail.com>
On Tue, May 18, 2021 at 01:07:55PM -0700, Yang Shi wrote:
> Add orig_pmd to struct vm_fault so the "orig_pmd" parameter used by huge page
> fault could be removed, just like its PTE counterpart does.
>
> Signed-off-by: Yang Shi <shy828301@gmail.com>
Acked-by: Mel Gorman <mgorman@suse.de>
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2021-05-19 8:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 20:07 [v3 PATCH 0/7] mm: thp: use generic THP migration for NUMA hinting fault Yang Shi
2021-05-18 20:07 ` [v3 PATCH 1/7] mm: memory: add orig_pmd to struct vm_fault Yang Shi
2021-05-19 8:13 ` Mel Gorman [this message]
2021-05-18 20:07 ` [v3 PATCH 2/7] mm: memory: make numa_migrate_prep() non-static Yang Shi
2021-05-18 20:07 ` [v3 PATCH 3/7] mm: thp: refactor NUMA fault handling Yang Shi
2021-05-18 20:07 ` [v3 PATCH 4/7] mm: migrate: account THP NUMA migration counters correctly Yang Shi
2021-05-18 20:07 ` [v3 PATCH 5/7] mm: migrate: don't split THP for misplaced NUMA page Yang Shi
2021-05-18 20:08 ` [v3 PATCH 6/7] mm: migrate: check mapcount for THP instead of refcount Yang Shi
2021-05-18 20:08 ` [v3 PATCH 7/7] mm: thp: skip make PMD PROT_NONE if THP migration is not supported Yang Shi
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=20210519081312.GC3672@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=shy828301@gmail.com \
--cc=ying.huang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.