From: Dave Airlie <airlied@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Kairui Song <ryncsn@gmail.com>,
Dave Chinner <david@fromorbit.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: list_lru isolate callback question?
Date: Fri, 6 Jun 2025 06:59:16 +1000 [thread overview]
Message-ID: <CAPM=9twVCz0AaoGWOLvZQ1ww9w5NVGsOrjBdavA1Mz0JDgD0mQ@mail.gmail.com> (raw)
In-Reply-To: <aEGhZZpTTwG2lXnq@casper.infradead.org>
On Thu, 5 Jun 2025 at 23:53, Matthew Wilcox <willy@infradead.org> wrote:
>
> On Thu, Jun 05, 2025 at 07:22:23PM +1000, Dave Airlie wrote:
> > Not slab objects, but I do have pages so I'm using page_to_nid right now,
> > however these pages aren't currently setting p->memcg_data as I don't
> > need that for this, but maybe
> > this gives me a reason to go down that road.
>
> Please don't. ->memcg_data is moving from struct page to the containing
> object (slab/folio/...)
I think I'd like to move all the code in the TTM page pooling handling
to folios, but I started pulling the thread one day and realised I had
no idea what I was doing when it came to knowing what I was doing.
I think porting all the x86 set_pages_* interfaces was where I think I
needed to start.
Dave.
next prev parent reply other threads:[~2025-06-05 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 2:16 Dave Airlie
2025-06-05 7:55 ` Kairui Song
2025-06-05 9:22 ` Dave Airlie
2025-06-05 13:53 ` Matthew Wilcox
2025-06-05 20:59 ` Dave Airlie [this message]
2025-06-05 22:39 ` Dave Chinner
2025-06-05 22:59 ` Dave Airlie
2025-06-10 22:44 ` Dave Chinner
2025-06-11 1:40 ` Dave Airlie
2025-06-10 23:07 ` Balbir Singh
2025-06-11 1:43 ` Dave Airlie
2025-06-11 22:34 ` Balbir Singh
2025-06-11 3:36 ` Matthew Wilcox
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='CAPM=9twVCz0AaoGWOLvZQ1ww9w5NVGsOrjBdavA1Mz0JDgD0mQ@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=david@fromorbit.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=ryncsn@gmail.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