From: Gregory Price <gourry@gourry.net>
To: "Harry (Hyeonggon) Yoo" <42.hyeyoo@gmail.com>
Cc: Honggyu Kim <honggyu.kim@sk.com>,
Byungchul Park <byungchul@sk.com>,
kernel_team@skhynix.com, Matthew Wilcox <willy@infradead.org>,
lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
linux-cxl@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] Restricting or migrating unmovable kernel allocations from slow tier
Date: Mon, 10 Feb 2025 01:00:02 -0500 [thread overview]
Message-ID: <Z6mV4vwkP0weiLie@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <Z6lli5cRHh1Ffvql@MacBook-Air-5.local>
On Mon, Feb 10, 2025 at 11:33:47AM +0900, Harry (Hyeonggon) Yoo wrote:
>
> Premise: Some ZONE_NORMAL capacity exists on CXL memory
> due to its large capacity.
>
What you actually need to show to justify increasing the complexity is
(at least - but not limited to)
1) structures you want to migrate are harmful when placed on slow memory
ex) Is `struct page` on slow mem actually harmful? - no data?
ex) Are page tables on slow mem actually harmful? - known, yes.
2) The structures cannot be made to take up less space on local tier
ex) struct page can be shrunk - do that first
ex) huge-pages can be deployed - do that first
3) the structures take up sufficient space that it matters
ex) struct page after shrunk might not - do that first
ex) page tables with multi-sized huge pages may not - do that first
4) Making the structures migratable actually does something useful
are `struct page` or page tables after #2 and #3 both:
a) going through hot/cold phases enough to warrant being tiered
b) hot enough for long enough that migration matters?
You can probably actually (maybe?) collect data on this today - but
you still have to contend with #2 and #3.
>
> I don't understand why we shouldn't introduce more kernel movable memory
> if that turns out to be beneficial?
>
No one is going to stop research you want to do. I'm simply expressing
that I think it's an ill-advised path to take.
~Gregory
next prev parent reply other threads:[~2025-02-10 6:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 13:29 Hyeonggon Yoo
2025-02-01 14:04 ` Matthew Wilcox
2025-02-01 15:13 ` Hyeonggon Yoo
2025-02-01 16:30 ` Gregory Price
2025-02-01 18:48 ` Matthew Wilcox
2025-02-03 22:09 ` Dan Williams
2025-02-07 7:20 ` Byungchul Park
2025-02-07 8:57 ` Gregory Price
2025-02-07 9:27 ` Gregory Price
2025-02-07 9:34 ` Honggyu Kim
2025-02-07 9:54 ` Gregory Price
2025-02-07 10:49 ` Byungchul Park
2025-02-10 2:33 ` Harry (Hyeonggon) Yoo
2025-02-10 3:19 ` Matthew Wilcox
2025-02-10 6:00 ` Gregory Price [this message]
2025-02-10 7:17 ` Byungchul Park
2025-02-10 15:47 ` Gregory Price
2025-02-10 15:55 ` Matthew Wilcox
2025-02-10 16:06 ` Gregory Price
2025-02-11 1:53 ` Byungchul Park
2025-02-21 1:52 ` Harry Yoo
2025-02-25 4:54 ` [LSF/MM/BPF TOPIC] Gathering ideas to reduce ZONE_NORMAL cost Byungchul Park
2025-02-25 5:06 ` [LSF/MM/BPF TOPIC] Restricting or migrating unmovable kernel allocations from slow tier Byungchul Park
2025-03-03 15:55 ` Gregory Price
2025-02-07 10:14 ` Byungchul Park
2025-02-10 7:02 ` Byungchul Park
2025-02-04 9:59 ` 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=Z6mV4vwkP0weiLie@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=42.hyeyoo@gmail.com \
--cc=byungchul@sk.com \
--cc=honggyu.kim@sk.com \
--cc=kernel_team@skhynix.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--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