From: dd <zhongling0719@126.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: zenghongling <zenghongling@kylinos.cn>,
dennis@kernel.org, tj@kernel.org, cl@gentwo.org,
linux-mm@kvack.org
Subject: Re:Re: [PATCH] mm/percpu-internal.h: optimise pcpu_chunk_struct to save memory
Date: Fri, 27 Mar 2026 15:08:05 +0800 (CST) [thread overview]
Message-ID: <2fcf4b59.518a.19d2e1f207b.Coremail.zhongling0719@126.com> (raw)
In-Reply-To: <20260326221641.7a2edff04ebb51561c8818e4@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]
Hi:
You may refer to the pahole test results before and after the modification. The offsets of other members remain unchanged. Originally, nr_empty_pop_pageswas placed alone at the beginning of the third cache line.
After the modification, it has been moved to the end of the second cache line.
Thanks.
At 2026-03-27 13:16:41, "Andrew Morton" <akpm@linux-foundation.org> wrote:
>On Thu, 5 Mar 2026 15:30:43 +0800 zenghongling <zenghongling@kylinos.cn> wrote:
>
>> Subject: [PATCH] mm/percpu-internal.h: optimise pcpu_chunk_struct to save memory
>
>There is no pcpu_chunk_struct, I'll change this to "struct pcpu_chunk".
>
>> Date: Thu, 5 Mar 2026 15:30:43 +0800
>> Sender: owner-linux-mm@kvack.org
>> X-Mailer: git-send-email 2.25.1
>>
>> The pcpu_chunk_struct has a hole of 4 bytes and pushes the struct to three
>> cachelines. Relocating the three booleans upwards allows for the struct
>> to only use two cachelines.
>
>before:
>
>(gdb) p sizeof(struct pcpu_chunk)
>$2 = 256
>
>after:
>
>(gdb) p sizeof(struct pcpu_chunk)
>$1 = 192
>
>That's remarkable. It was an allmodconfig build which tends to add
>bloat, but the only source-level alteration was this patch.
>
>
>Another consideration here is that moving members around can have a
>performance impact - it can cause more (or less) cacheline
>invalidations. I worry that because someone has carefully commented
>all the member offsets, this might have been a consideration.
>
>Also I think your patch may have made those comments incorrect?
>
>
>Dennis, Tejun, Christoph: I think we want this space saving. Can
>you please advise?
>
>Thanks.
[-- Attachment #2: Type: text/html, Size: 2153 bytes --]
next prev parent reply other threads:[~2026-03-27 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 7:30 zenghongling
2026-03-27 5:16 ` Andrew Morton
2026-03-27 7:08 ` dd [this message]
2026-03-27 7:32 ` Dennis Zhou
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=2fcf4b59.518a.19d2e1f207b.Coremail.zhongling0719@126.com \
--to=zhongling0719@126.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=dennis@kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.org \
--cc=zenghongling@kylinos.cn \
/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