All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: David Hildenbrand <david@redhat.com>
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 16:11:55 +0000	[thread overview]
Message-ID: <Z1m5y0R5fttFN5o8@casper.infradead.org> (raw)
In-Reply-To: <42869071-64a9-47d1-867d-9ddede6bf430@redhat.com>

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?)


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 11:55 The future of PageAnonExclusive 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 [this message]
2024-12-11 16:15             ` David Hildenbrand

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=Z1m5y0R5fttFN5o8@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.