From: wangxuewen <18810879172@163.com>
To: David Hildenbrand <david@redhat.com>, akpm@linux-foundation.org
Cc: zhengqi.arch@bytedance.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, wangxuewen <wangxuewen@kylinos.cn>
Subject: Re: [PATCH v1] mm/vmscan: Account hwpoisoned folios in reclaim statistics
Date: Fri, 4 Jul 2025 11:14:13 +0800 [thread overview]
Message-ID: <e2b183cd-dfd7-4eb2-b454-8966e695a9b4@163.com> (raw)
In-Reply-To: <32a0cfdd-3f6e-47af-86f6-248149ae51ae@redhat.com>
> Hi David,
>
> Thank you for your insightful feedback. You make an excellent point -
> hwpoisoned pages are indeed not truly "reclaimed" as they don't contribute
> to available memory but represent permanently lost capacity.
>
> I will drop this patch.
>
> Best regards,
> wangxuewen
在 2025/7/2 17:44, David Hildenbrand 写道:
> On 02.07.25 11:34, 18810879172@163.com wrote:
>> From: wangxuewen <wangxuewen@kylinos.cn>
>>
>> When encountering a hardware-poisoned folio in shrink_folio_list(),
>> we unmap and release the folio but fail to account it in the reclaim
>> statistics (sc->nr_reclaimed). This leads to an undercount of
>> actually reclaimed pages, potentially causing unnecessary additional
>> reclaim pressure.
>
> I'll just note that this kind-of makes sense: the memory is not actually
> reclaimed -- we don't get free memory back. The hwpoisoned page is lost.
>
prev parent reply other threads:[~2025-07-04 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 9:34 18810879172
2025-07-02 9:44 ` David Hildenbrand
2025-07-04 3:14 ` wangxuewen [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=e2b183cd-dfd7-4eb2-b454-8966e695a9b4@163.com \
--to=18810879172@163.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wangxuewen@kylinos.cn \
--cc=zhengqi.arch@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