mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] debugobjects: Allow bigger number of objects
Date: Tue, 26 Jan 2016 21:22:12 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1601262121220.3886@nanos> (raw)
In-Reply-To: <1453461761-14761-1-git-send-email-borntraeger@de.ibm.com>

On Fri, 22 Jan 2016, Christian Borntraeger wrote:

> On my bigger s390 systems  I always get
> "Out of memory. ODEBUG disabled". Since the number of objects
> is needed at compile time in the code, let's provide a Kconfig
> variable to increase the number of static objects.

How many do you need on those big machines? Can't we scale that automagically
with the number of cpus or such?

Thanks,

	tglx
 
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
>  lib/Kconfig.debug  | 11 +++++++++++
>  lib/debugobjects.c |  2 +-
>  2 files changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 8c15b29..dc44b6f 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -453,6 +453,17 @@ config DEBUG_OBJECTS_ENABLE_DEFAULT
>          help
>            Debug objects boot parameter default value
>  
> +config DEBUG_OBJECTS_STATIC_ELEMENTS
> +	int "debug_objects static element buffer size (100-10000)"
> +	range 100 10000
> +	default "500"
> +	depends on DEBUG_OBJECTS
> +	help
> +	  How many static objects can be stored at early boot time. If this
> +	  value is exceeded object debugging will stop with an message
> +	  "Out of memory. ODEBUG disabled". Higher values will allocate a
> +	  bigger static buffer, but this buffer will be released later on.
> +
>  config DEBUG_SLAB
>  	bool "Debug slab memory allocations"
>  	depends on DEBUG_KERNEL && SLAB && !KMEMCHECK
> diff --git a/lib/debugobjects.c b/lib/debugobjects.c
> index 547f7f9..fc4ae86 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	CONFIG_DEBUG_OBJECTS_STATIC_ELEMENTS
>  #define ODEBUG_POOL_MIN_LEVEL	256
>  
>  #define ODEBUG_CHUNK_SHIFT	PAGE_SHIFT
> -- 
> 2.3.0
> 
> 

  reply	other threads:[~2016-01-26 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 11:22 Christian Borntraeger
2016-01-26 20:22 ` Thomas Gleixner [this message]
2016-01-27 12:42   ` Christian Borntraeger
2016-01-27 13:37     ` 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=alpine.DEB.2.11.1601262121220.3886@nanos \
    --to=tglx@linutronix.de \
    --cc=borntraeger@de.ibm.com \
    --cc=linux-kernel@vger.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®