From: David Hildenbrand <david@redhat.com>
To: Xueshi Hu <xueshi.hu@smartx.com>,
mike.kravetz@oracle.com, muchun.song@linux.dev, corbet@lwn.net,
akpm@linux-foundation.org, n-horiguchi@ah.jp.nec.com,
osalvador@suse.de
Cc: linux-mm@kvack.org
Subject: Re: [PATCH v2 2/4] mm/hugeltb: clean up hstate::max_huge_pages
Date: Mon, 7 Aug 2023 17:17:00 +0200 [thread overview]
Message-ID: <5ef201cd-dd30-45c7-9f49-c5e6301e8652@redhat.com> (raw)
In-Reply-To: <20230806074853.317203-3-xueshi.hu@smartx.com>
On 06.08.23 09:48, Xueshi Hu wrote:
> Presently, the sole use case of hstate::max_huge_pages is confined to
> hugetlb_sysctl_handler_common() and hugetlbfs_size_to_hpages().
> The former has been replaced with hstate::nr_huge_pages, while the latter
Most probably that conversion is wrong as it changes documented
behavior, and therefore, this patch is not applicable.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-08-07 15:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 7:48 [PATCH v2 0/4] mm/hugetlb: fix /sys and /proc fs dealing with persistent hugepages Xueshi Hu
2023-08-06 7:48 ` [PATCH v2 1/4] mm/hugetlb: fix the inconsistency of /proc/sys/vm/nr_huge_pages Xueshi Hu
2023-08-07 15:15 ` David Hildenbrand
2023-08-08 2:28 ` Xueshi Hu
2023-08-08 7:58 ` David Hildenbrand
2023-08-08 9:13 ` Xueshi Hu
2023-08-10 0:17 ` Mike Kravetz
2023-08-10 7:34 ` David Hildenbrand
2023-08-10 22:15 ` Mike Kravetz
2023-08-25 4:02 ` Xueshi Hu
2023-08-25 21:15 ` Mike Kravetz
2023-08-26 2:51 ` Xueshi Hu
2023-08-06 7:48 ` [PATCH v2 2/4] mm/hugeltb: clean up hstate::max_huge_pages Xueshi Hu
2023-08-07 15:17 ` David Hildenbrand [this message]
2023-08-06 7:48 ` [PATCH v2 3/4] mm/hugeltb: fix nodes huge page allocation when there are surplus pages Xueshi Hu
2023-08-06 7:48 ` [PATCH v2 4/4] docs: hugetlbpage.rst: make the meaning of persistent hugetlb pages clear Xueshi Hu
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=5ef201cd-dd30-45c7-9f49-c5e6301e8652@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=osalvador@suse.de \
--cc=xueshi.hu@smartx.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