From: Joao Correia <joaomiguelcorreia@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: LKML <linux-kernel@vger.kernel.org>,
Amerigo Wang <xiyou.wangcong@gmail.com>
Subject: Re: [PATCH 3/3] Increase lockdep limits: MAX_LOCKDEP_CHAINS_BITS
Date: Wed, 8 Jul 2009 20:33:37 +0100 [thread overview]
Message-ID: <a5d9929e0907081233s6fc42c15k710047a1b0dcc5bf@mail.gmail.com> (raw)
In-Reply-To: <a5d9929e0907081232y2c043a05lff8868c3c5931e9e@mail.gmail.com>
On Wed, Jul 8, 2009 at 8:32 PM, Joao Correia<joaomiguelcorreia@gmail.com> wrote:
> On Wed, Jul 8, 2009 at 7:34 PM, Peter Zijlstra<a.p.zijlstra@chello.nl> wrote:
>> On Tue, 2009-07-07 at 16:25 +0100, Joao Correia wrote:
>>> (Applies to current Linus tree, as of 2.6.31-rc2)
>>>
>>> A third limit becomes apparent as being too low after raising
>>> MAX_STACK_TRACE_ENTRIES and MAX_LOCK_DEPTH, although this one is more
>>> elusive to trigger.
>>
>> Would this involve reloading modules a lot?
>>
>>
>
> All the other limits were triggered immediatly upon boot. This one
> happens during regular system usage, after a couple of hours. Not
> loading more modules than needed, the system stays at around 45
> modules loaded, give or take. I do have qemu running, if that helps
> anything.
>
> Joao Correia
>
qemu running as a -host-, not the system running inside it. Just to clear it up.
Joao Correia
next prev parent reply other threads:[~2009-07-08 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 15:25 Joao Correia
2009-07-07 15:32 ` Peter Zijlstra
2009-07-08 18:34 ` Peter Zijlstra
2009-07-08 19:32 ` Joao Correia
2009-07-08 19:33 ` Joao Correia [this message]
2009-07-10 20:34 ` Dave Jones
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=a5d9929e0907081233s6fc42c15k710047a1b0dcc5bf@mail.gmail.com \
--to=joaomiguelcorreia@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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®