linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: The future of PageAnonExclusive
Date: Wed, 11 Dec 2024 17:15:10 +0100	[thread overview]
Message-ID: <598b5386-16f9-41e6-95e4-93f5ac32fb64@redhat.com> (raw)
In-Reply-To: <Z1m5y0R5fttFN5o8@casper.infradead.org>

On 11.12.24 17:11, Matthew Wilcox wrote:
> On Wed, Dec 11, 2024 at 04:50:12PM +0100, David Hildenbrand wrote:
>> On 11.12.24 16:45, Matthew Wilcox wrote:
>>> [1] https://kernelnewbies.org/MatthewWilcox/Memdescs
>>>
>>> Don't get too excited about "we're almost out of types".  The "managed"
>>> type has subtypes.  We could also collapse "file" and "anon" into a
>>> single type and distinguish between them with a bit in the folio.
>>>
>>> Anyway, yes, we can do one per-page flag.  Two per-page flags starts to
>>> get dicey.
>>
>> hwpoison? :/
> 
> type 9!  My thinking is that the hwpoison type contains an orig_memdesc
> field, as well as whatever else is needed to describe the hwpoison that
> was discovered (start, length, what else?)

Ah, I see. So you'd have to allocate that type during a MCE, and have 
all file/anon detection code respect that indirection as well.

-- 
Cheers,

David / dhildenb



      reply	other threads:[~2024-12-11 16:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 11:55 David Hildenbrand
2024-12-11 11:56 ` David Hildenbrand
2024-12-11 13:42   ` Kirill A. Shutemov
2024-12-11 13:48     ` David Hildenbrand
2024-12-11 14:25   ` Ryan Roberts
2024-12-11 14:49     ` David Hildenbrand
2024-12-11 15:45       ` Matthew Wilcox
2024-12-11 15:50         ` David Hildenbrand
2024-12-11 16:11           ` Matthew Wilcox
2024-12-11 16:15             ` David Hildenbrand [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=598b5386-16f9-41e6-95e4-93f5ac32fb64@redhat.com \
    --to=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.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