From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Jiaqi Yan <jiaqiyan@google.com>,
mike.kravetz@oracle.com, naoya.horiguchi@nec.com,
songmuchun@bytedance.com, shy828301@gmail.com,
linmiaohe@huawei.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, duenwen@google.com,
axelrasmussen@google.com, jthoughton@google.com
Subject: Re: [PATCH v3 2/4] mm/hwpoison: check if a subpage of a hugetlb folio is raw HWPOISON
Date: Fri, 7 Jul 2023 14:05:51 -0700 [thread overview]
Message-ID: <20230707140551.07e06293e4943be0c6c557fe@linux-foundation.org> (raw)
In-Reply-To: <ZKh2K7ObVtlXHkTk@casper.infradead.org>
On Fri, 7 Jul 2023 21:31:39 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> On Fri, Jul 07, 2023 at 08:19:02PM +0000, Jiaqi Yan wrote:
> > Add the functionality, is_raw_hwp_subpage, to tell if a subpage of a
>
> This is incorrect naming. "subpage" was needed before we had the
> folio concept, but it should not be used any more. We have folios
> and pages now.
>
> Also, abbreviating "hwpoison" as "hwp" seems like a bad idea to me.
> hwp is already used as an acronym by acpi, intel_pstate, some clock
> drivers, an ethernet driver, and a scsi driver.
Thanks, Matthew. I'll merge v3 so we hit next -next (which actually
won't be until Monday), and add a note that v4 is expected.
next prev parent reply other threads:[~2023-07-07 21:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 20:19 [PATCH v3 0/4] Improve hugetlbfs read on HWPOISON hugepages Jiaqi Yan
2023-07-07 20:19 ` [PATCH v3 1/4] mm/hwpoison: delete all entries before traversal in __folio_free_raw_hwp Jiaqi Yan
2023-07-08 2:40 ` Miaohe Lin
2023-07-07 20:19 ` [PATCH v3 2/4] mm/hwpoison: check if a subpage of a hugetlb folio is raw HWPOISON Jiaqi Yan
2023-07-07 20:31 ` Matthew Wilcox
2023-07-07 21:05 ` Andrew Morton [this message]
2023-07-10 0:21 ` Naoya Horiguchi
2023-07-10 15:11 ` Jiaqi Yan
2023-07-11 8:59 ` Naoya Horiguchi
2023-07-08 2:57 ` Miaohe Lin
2023-07-10 15:16 ` Jiaqi Yan
2023-07-11 17:05 ` Jiaqi Yan
2023-07-11 18:01 ` Mike Kravetz
2023-07-11 22:22 ` Jiaqi Yan
2023-07-12 2:25 ` Miaohe Lin
2023-07-07 20:19 ` [PATCH v3 3/4] hugetlbfs: improve read HWPOISON hugepage Jiaqi Yan
2023-07-07 20:19 ` [PATCH v3 4/4] selftests/mm: add tests for HWPOISON hugetlbfs read Jiaqi Yan
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=20230707140551.07e06293e4943be0c6c557fe@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=duenwen@google.com \
--cc=jiaqiyan@google.com \
--cc=jthoughton@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=shy828301@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=willy@infradead.org \
/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