From: Babu Moger <babu.moger@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, akpm@linux-foundation.org,
keescook@chromium.org, dan.j.williams@intel.com,
aryabinin@virtuozzo.com, tj@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Ajust lockdep static allocations
Date: Fri, 23 Sep 2016 10:15:46 -0500 [thread overview]
Message-ID: <842fdad9-638e-f98c-5e3d-c3e698943e30@oracle.com> (raw)
In-Reply-To: <20160923150439.GD5012@twins.programming.kicks-ass.net>
On 9/23/2016 10:04 AM, Peter Zijlstra wrote:
> On Fri, Sep 23, 2016 at 09:50:52AM -0500, Babu Moger wrote:
>>> Why can't you boot? You have that little memories? 4MB doesn't seem like
>>> a worthwhile amount of memory.
>>>
>>> Also, you didn't say. This seems a somewhat crucial point.
>> Correct, We can't boot with lockdep. Sorry I did not make that clear.
>> We have a limit on static size of the kernel.
> This stuff should be in .bss not .data. It should not affect the static
> size at all. Or am I misunderstanding things?
Here it is.
$ ./scripts/bloat-o-meter vmlinux.lockdep.small vmlinux.lockdep.big
add/remove: 0/0 grow/shrink: 5/0 up/down: 4653056/0 (4653056)
function old new delta
stack_trace 2097152 4194304 +2097152
lock_chains 1048576 2097152 +1048576
list_entries 1048576 2097152 +1048576
chain_hlocks 327680 655360 +327680
chainhash_table 131072 262144 +131072
Total: Before=21046200, After=25699256, chg 22.000000%
next prev parent reply other threads:[~2016-09-23 15:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 18:43 Babu Moger
2016-09-22 18:43 ` [PATCH 1/2] lockdep: Keep the default static allocations small Babu Moger
2016-09-22 18:43 ` [PATCH 2/2] config: Add new CONFIG_PROVE_LOCKING_PLUS Babu Moger
2016-09-23 7:12 ` [PATCH 0/2] Ajust lockdep static allocations Peter Zijlstra
2016-09-23 14:04 ` Babu Moger
2016-09-23 14:34 ` Peter Zijlstra
2016-09-23 14:50 ` Babu Moger
2016-09-23 15:04 ` Peter Zijlstra
2016-09-23 15:15 ` Babu Moger [this message]
2016-09-23 15:40 ` Peter Zijlstra
2016-09-23 19:57 ` Babu Moger
2016-09-23 20:08 ` Rob Gardner
2016-09-23 20:17 ` Peter Zijlstra
2016-09-23 20:30 ` Babu Moger
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=842fdad9-638e-f98c-5e3d-c3e698943e30@oracle.com \
--to=babu.moger@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dan.j.williams@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tj@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®