From: Mateusz Guzik <mjguzik@gmail.com>
To: Harry Yoo <harry.yoo@oracle.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
linux-mm <linux-mm@kvack.org>, Dennis Zhou <dennis@kernel.org>
Subject: Re: a case for a destructor for slub: mm_struct
Date: Mon, 17 Mar 2025 10:23:52 +0100 [thread overview]
Message-ID: <CAGudoHEoOHsU+8AXRBp1DNQZOz6PiZGFB_6gFdpBM06oh1XfWQ@mail.gmail.com> (raw)
In-Reply-To: <Z9e2L7TGIvZgwDXB@harry>
On Mon, Mar 17, 2025 at 6:42 AM Harry Yoo <harry.yoo@oracle.com> wrote:
> If we allow reclaiming per-cpu stuff only biut do not reclaim
> the slab object that contains it...
>
> Does that mean the users of the cache need to check if the percpu
> memory has been reclaimed and if so, should call init routines (e.g.,
> mm_init())?
>
see the other mail (about to be written) e-mail.
> > I'm happy to split the churn and add some 'return 0;' myself.
>
> Fortunately, there were only a handful users of of constructor ;-)
> Never mind, I converted all of them in an hour (splitting the work + ping
> pong-ing seemed like unnecessary overhead).
>
cool and apologies again :)
> Will send the patch series before too late.
> But please be patient—since LSFMM is next week,
> I'm expecting to be busier than usual :)
>
there is zero time pressure here mate
I appreciate you looking into this.
--
Mateusz Guzik <mjguzik gmail.com>
prev parent reply other threads:[~2025-03-17 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 10:33 Mateusz Guzik
2025-03-13 8:59 ` Harry Yoo
2025-03-13 11:23 ` Mateusz Guzik
2025-03-13 11:25 ` Mateusz Guzik
2025-03-14 8:27 ` Harry Yoo
2025-03-14 8:34 ` Harry Yoo
2025-03-14 12:32 ` Mateusz Guzik
2025-03-17 5:42 ` Harry Yoo
2025-03-17 9:02 ` Vlastimil Babka
2025-03-17 9:17 ` Mateusz Guzik
2025-03-17 9:23 ` Mateusz Guzik [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=CAGudoHEoOHsU+8AXRBp1DNQZOz6PiZGFB_6gFdpBM06oh1XfWQ@mail.gmail.com \
--to=mjguzik@gmail.com \
--cc=42.hyeyoo@gmail.com \
--cc=dennis@kernel.org \
--cc=harry.yoo@oracle.com \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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