From: tip-bot for Christian Borntraeger <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: borntraeger@de.ibm.com, mingo@kernel.org, hpa@zytor.com,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: [tip:core/urgent] debugobjects: Allow bigger number of early boot objects
Date: Wed, 27 Jan 2016 06:45:37 -0800 [thread overview]
Message-ID: <tip-0b6ec8c0a3708f0a54b75ee1200772ec5226ec49@git.kernel.org> (raw)
In-Reply-To: <1453905478-13409-1-git-send-email-borntraeger@de.ibm.com>
Commit-ID: 0b6ec8c0a3708f0a54b75ee1200772ec5226ec49
Gitweb: http://git.kernel.org/tip/0b6ec8c0a3708f0a54b75ee1200772ec5226ec49
Author: Christian Borntraeger <borntraeger@de.ibm.com>
AuthorDate: Wed, 27 Jan 2016 15:37:58 +0100
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Wed, 27 Jan 2016 15:40:59 +0100
debugobjects: Allow bigger number of early boot objects
On my bigger s390 systems I always get "Out of memory.
ODEBUG disabled". Since the number of objects is needed at
compile time, we can not change the size dynamically before
the caches etc are available. Doubling the size seems to
do the trick. Since it is init data it will be freed anyway,
this should be ok.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Link: http://lkml.kernel.org/r/1453905478-13409-1-git-send-email-borntraeger@de.ibm.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
lib/debugobjects.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/debugobjects.c b/lib/debugobjects.c
index 547f7f9..519b5a1 100644
--- a/lib/debugobjects.c
+++ b/lib/debugobjects.c
@@ -21,7 +21,7 @@
#define ODEBUG_HASH_BITS 14
#define ODEBUG_HASH_SIZE (1 << ODEBUG_HASH_BITS)
-#define ODEBUG_POOL_SIZE 512
+#define ODEBUG_POOL_SIZE 1024
#define ODEBUG_POOL_MIN_LEVEL 256
#define ODEBUG_CHUNK_SHIFT PAGE_SHIFT
prev parent reply other threads:[~2016-01-27 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 14:37 [PATCH v2] debugobjects: Allow bigger number of objects Christian Borntraeger
2016-01-27 14:45 ` tip-bot for Christian Borntraeger [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=tip-0b6ec8c0a3708f0a54b75ee1200772ec5226ec49@git.kernel.org \
--to=tipbot@zytor.com \
--cc=borntraeger@de.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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®