linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Kairui Song <ryncsn@gmail.com>
Cc: 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: Thu, 5 Jun 2025 19:22:23 +1000	[thread overview]
Message-ID: <CAPM=9tyrvdm54LBcitudB06eRYX0BhNd_8mMtE_jTVEzY7G7Cw@mail.gmail.com> (raw)
In-Reply-To: <CAMgjq7DGEewWzqzc0717DhxA73uv00VRjWxdiyo3TrO9MSANwA@mail.gmail.com>

On Thu, 5 Jun 2025 at 17:55, Kairui Song <ryncsn@gmail.com> wrote:
>
> On Thu, Jun 5, 2025 at 10:17 AM Dave Airlie <airlied@gmail.com> wrote:
> >
> > I've hit a case where I think it might be valuable to have the nid +
> > struct memcg for the item being iterated available in the isolate
> > callback, I know in theory we should be able to retrieve it from the
> > item, but I'm also not convinced we should need to since we have it
> > already in the outer function?
> >
> > typedef enum lru_status (*list_lru_walk_cb)(struct list_head *item,
> >                         struct list_lru_one *list,
> >                         int nid,
> >                         struct mem_cgroup *memcg,
> >                         void *cb_arg);
> >
>
> Hi Dave,
>
> > It's probably not essential (I think I can get the nid back easily,
> > not sure about the memcg yet), but I thought I'd ask if there would be
>
> If it's a slab object you should be able to get it easily with:
> memcg = mem_cgroup_from_slab_obj(item));
> nid = page_to_nid(virt_to_page(item));
>

It's in relation to some work trying to tie GPU system memory
allocations into memcg properly,

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.

> > resistance against just adding them to the callback?
>
> I'm not sure about the context here, I personally prefer to keep the
> function minimized unless necessary, so things like !CONFIG_MEMCG or
> single node builds won't have two dummy parameters here, and
> most caller won't need them, the compiler can't optimize that
> out IIUC.

I reconsidered and was wondering if

struct lru_walk_args {
    struct list_lru_one *list;
    int nid;
    struct mem_cgroup *memcg;
}
would also be an option instead of adding two unused args.

But I'll see if I can make it work once I get the memcg pieces of the
puzzle sorted out.

Dave.
>
> >
> > Dave.
> >


  reply	other threads:[~2025-06-05  9:22 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 [this message]
2025-06-05 13:53     ` Matthew Wilcox
2025-06-05 20:59       ` Dave Airlie
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=9tyrvdm54LBcitudB06eRYX0BhNd_8mMtE_jTVEzY7G7Cw@mail.gmail.com' \
    --to=airlied@gmail.com \
    --cc=david@fromorbit.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=ryncsn@gmail.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