From: Peter Zijlstra <peterz@infradead.org>
To: John Kacur <jkacur@redhat.com>
Cc: mingo@elte.hu, tglx@linuxtronix.de, linux-kernel@vger.kernel.org,
Clark Williams <williams@redhat.com>
Subject: Re: [PATCH] Increase MAX_STACK_TRACE_ENTRIES
Date: Tue, 22 Sep 2009 13:29:22 +0200 [thread overview]
Message-ID: <1253618962.7695.43.camel@twins> (raw)
In-Reply-To: <alpine.LFD.2.00.0909211744230.6572@localhost.localdomain>
On Mon, 2009-09-21 at 19:13 +0200, John Kacur wrote:
> Ingo: please consider this patch if there are no negative consequences to
> increasing this value. It fixes a problem that we have seen in the past on
> (at least) the real-time kernel. (BUG: MAX_STACK_TRACE_ENTRIES).
>
> This patch applies to the current tip/master
Hrmm,.. this is growing to be very large indeed.
It would be nice to know where all these extra entries are coming from.
How large are:
# cat /proc/lockdep | grep -v -e "\->" -e "^$" | wc -l
437
# cat /proc/lockdep | grep -v -e "\->" -e "^$" | awk '{print $6}' |
tr -d ".:" | grep -v "^$" | wc -c
1031
On your machine?
> -#define MAX_STACK_TRACE_ENTRIES 262144UL
> +#define MAX_STACK_TRACE_ENTRIES 393216UL
prev parent reply other threads:[~2009-09-22 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 17:13 John Kacur
2009-09-22 11:29 ` Peter Zijlstra [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=1253618962.7695.43.camel@twins \
--to=peterz@infradead.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linuxtronix.de \
--cc=williams@redhat.com \
/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®