From: Oscar Salvador <osalvador@suse.de>
To: akpm@linux-foundation.org
Cc: mhocko@suse.com, mike.kravetz@oracle.com,
mm-commits@vger.kernel.org, songmuchun@bytedance.com
Subject: Re: + hugetlb-use-pageprivate-for-hugetlb-specific-page-flags-fix-2.patch added to -mm tree
Date: Wed, 24 Feb 2021 09:11:58 +0100 [thread overview]
Message-ID: <9aa21b52622cbb9dd7bb8cb6be110f1c@suse.de> (raw)
In-Reply-To: <20210224042858.x12k3SMNe%akpm@linux-foundation.org>
On 2021-02-24 05:28, akpm@linux-foundation.org wrote:
> The patch titled
> Subject: hugetlb: document the new location of page subpool
> pointer
> has been added to the -mm tree. Its filename is
>
> hugetlb-use-pageprivate-for-hugetlb-specific-page-flags-fix-2.patch
>
> This patch should soon appear at
>
> https://ozlabs.org/~akpm/mmots/broken-out/hugetlb-use-pageprivate-for-hugetlb-specific-page-flags-fix-2.patch
> and later at
>
> https://ozlabs.org/~akpm/mmotm/broken-out/hugetlb-use-pageprivate-for-hugetlb-specific-page-flags-fix-2.patch
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/process/submit-checklist.rst when
> testing your code ***
>
> The -mm tree is included into linux-next and is updated
> there every 3-4 working days
>
> ------------------------------------------------------
> From: Mike Kravetz <mike.kravetz@oracle.com>
> Subject: hugetlb: document the new location of page subpool pointer
>
> Expand comments, no functional change.
>
> Link:
> https://lkml.kernel.org/r/20210224040439.351882-1-mike.kravetz@oracle.com
> Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Oscar Salvador <osalvador@suse.de>
> Cc: Muchun Song <songmuchun@bytedance.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Oscar Salvador <osalvador@suse.de>
> ---
>
> include/linux/hugetlb.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> ---
> a/include/linux/hugetlb.h~hugetlb-use-pageprivate-for-hugetlb-specific-page-flags-fix-2
> +++ a/include/linux/hugetlb.h
> @@ -476,6 +476,9 @@ unsigned long hugetlb_get_unmapped_area(
> * huegtlb page specific state flags. These flags are located in
> page.private
> * of the hugetlb head page. Functions created via the below macros
> should be
> * used to manipulate these flags.
> + * Note: The hugetlb page subpool pointer previously located at
> page.private
> + * was moved to page[1].private to make room for flags in the head
> page. See
> + * hugetlb_page_subpool().
> *
> * HPG_restore_reserve - Set when a hugetlb page consumes a
> reservation at
> * allocation time. Cleared when page is fully instantiated. Free
> _
>
> Patches currently in -mm which might be from mike.kravetz@oracle.com
> are
>
> hugetlb-fix-update_and_free_page-contig-page-struct-assumption.patch
> hugetlb-fix-copy_huge_page_from_user-contig-page-struct-assumption.patch
> hugetlb-use-pageprivate-for-hugetlb-specific-page-flags.patch
> hugetlb-use-pageprivate-for-hugetlb-specific-page-flags-fix.patch
> hugetlb-use-pageprivate-for-hugetlb-specific-page-flags-fix-2.patch
> hugetlb-convert-page_huge_active-hpagemigratable-flag.patch
> hugetlb-convert-pagehugetemporary-to-hpagetemporary-flag.patch
> hugetlb-convert-pagehugefreed-to-hpagefreed-flag.patch
> include-linux-hugetlbh-add-synchronization-information-for-new-hugetlb-specific-flags.patch
> mm-hugetlb-change-hugetlb_reserve_pages-to-type-bool.patch
> hugetlbfs-remove-special-hugetlbfs_set_page_dirty.patch
--
Oscar Salvador
SUSE L3
prev parent reply other threads:[~2021-02-24 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 4:28 + hugetlb-use-pageprivate-for-hugetlb-specific-page-flags-fix-2.patch added to -mm tree akpm
2021-02-24 8:11 ` Oscar Salvador [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=9aa21b52622cbb9dd7bb8cb6be110f1c@suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=mm-commits@vger.kernel.org \
--cc=songmuchun@bytedance.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