From: Andrew Morton <akpm@linux-foundation.org>
To: Benjamin Block <bblock@linux.ibm.com>
Cc: Thomas Gleixner <tglx@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Qian Cai <quic_qiancai@quicinc.com>
Subject: Re: [PATCH] debugobjects: Allow to configure the amount of pre-allocated objects
Date: Sat, 14 Mar 2026 15:06:49 -0700 [thread overview]
Message-ID: <20260314150649.9a7c4bf4554b1288eb471edc@linux-foundation.org> (raw)
In-Reply-To: <20260313142620.GG2161595@p1gen4-pw042f0m>
On Fri, 13 Mar 2026 15:26:20 +0100 Benjamin Block <bblock@linux.ibm.com> wrote:
> > obj_static_pool[] is __initdata, so the consequences of making it large
> > are very slight. So do we really need
> > CONFIG_DEBUG_OBJECTS_POOL_SIZE_SHIFT? Requiring a rebuild is a huge
> > hassle. How about simply making the static pool much larger and leave
> > it at that?
>
> I was thinking about that but then couldn't decide what would be "big enough"
> as constant value for "everyone". My test systems wasn't even that "big", and
> I'm already at 1280 KiB reservation to make ODEBUG "survive" the boot. Not
> sure I want to make this say 2 MiB without config option for everyone.
2MB of initmem probably just doesn't matter. Annoying.
Do you understand *why* s390 is using so many objects? Presumably the
current much smaller default is OK for most systems - my googling for
"Out of memory. ODEBUG disabled" turned up very little.
Oh, look what I found.
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1807440.html
What happened to that?
next prev parent reply other threads:[~2026-03-14 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 16:05 Benjamin Block
2026-03-11 10:04 ` Benjamin Block
2026-03-11 17:47 ` Andrew Morton
2026-03-13 14:26 ` Benjamin Block
2026-03-14 22:06 ` Andrew Morton [this message]
2026-03-17 11:42 ` Benjamin Block
2026-03-20 15:26 ` Thomas Gleixner
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=20260314150649.9a7c4bf4554b1288eb471edc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bblock@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=quic_qiancai@quicinc.com \
--cc=tglx@kernel.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
all inboxes | Powered by JetHome®