From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: "Jay Patel" <jaypatel@linux.ibm.com>,
"Brian “Binder” Makin" <merimus@google.com>,
linux-mm@kvack.org, cl@linux.com, penberg@kernel.org,
iamjoonsoo.kim@lge.com,
"Andrew Morton" <akpm@linux-foundation.org>,
"Vlastimil Babka" <vbabka@suse.cz>,
aneesh.kumar@linux.ibm.com, tsahu@linux.ibm.com,
piyushs@linux.ibm.com
Subject: Re: [PATCH] [RFC PATCH v2]mm/slub: Optimize slub memory usage
Date: Sun, 9 Jul 2023 23:42:08 +0900 [thread overview]
Message-ID: <CAB=+i9Taa51qcfQ3-cYy5Se=iHA+j-_QJ93NqKGfg=GmpPfyxQ@mail.gmail.com> (raw)
In-Reply-To: <b87d8eee-2ce5-b7d5-97f8-a5d80eed3c44@google.com>
On Mon, Jul 3, 2023 at 9:13 AM David Rientjes <rientjes@google.com> wrote:
>
> Thanks very much for looking at this, Jay!
>
> My colleague, Binder, has also been looking at opportunities to optimize
> memory usage when using SLUB. We're preparing to deprecate SLAB
> internally and shift toward SLUB since SLAB is scheduled for removal after
> the next LTS kernel.
>
> Binder, do you have an evaluation with this patch similar to what Jay did?
>
> Also, tangentially: we are looking at other opportunities for reduction in
> memory overhead when using SLUB. If you or anybody else are interested in
> being involved in a working group with this shared goal, please let me
> know. We could brainstorm, collaborate, and share data.
I'm also interested in reducing SLUB memory overhead!
I have some rough ideas, which should be evaluated further:
1. Lengthen or shrink number of cached objects per CPU based on
list_lock contention.
2. Modify SLUB to enable linking objects from different slabs into the
CPU freelist.
Do you have any opinions, or are there any approaches you are already examining?
--
Hyeonggon
next prev parent reply other threads:[~2023-07-09 14:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 9:57 Jay Patel
2023-07-03 0:13 ` David Rientjes
2023-07-03 8:39 ` Jay Patel
2023-07-09 14:42 ` Hyeonggon Yoo [this message]
2023-07-12 13:06 ` Vlastimil Babka
2023-07-20 10:30 ` Jay Patel
2023-07-17 13:41 ` kernel test robot
2023-07-18 6:43 ` Hyeonggon Yoo
2023-07-20 3:00 ` Oliver Sang
2023-07-20 12:59 ` Hyeonggon Yoo
2023-07-20 13:46 ` Hyeonggon Yoo
2023-07-20 14:15 ` Hyeonggon Yoo
2023-07-24 2:39 ` Oliver Sang
2023-07-31 9:49 ` Hyeonggon Yoo
2023-07-20 13:49 ` Feng Tang
2023-07-20 15:05 ` Hyeonggon Yoo
2023-07-21 14:50 ` Binder Makin
2023-07-21 15:39 ` Hyeonggon Yoo
2023-07-21 18:31 ` Binder Makin
2023-07-24 14:35 ` Feng Tang
2023-07-25 3:13 ` Hyeonggon Yoo
2023-07-25 9:12 ` Feng Tang
2023-08-29 8:30 ` Feng Tang
2023-07-26 10:06 ` Vlastimil Babka
2023-08-10 10:38 ` Jay Patel
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='CAB=+i9Taa51qcfQ3-cYy5Se=iHA+j-_QJ93NqKGfg=GmpPfyxQ@mail.gmail.com' \
--to=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jaypatel@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=merimus@google.com \
--cc=penberg@kernel.org \
--cc=piyushs@linux.ibm.com \
--cc=rientjes@google.com \
--cc=tsahu@linux.ibm.com \
--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