From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Ingo Molnar <mingo@elte.hu>,
mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] degrade severity of lockdep printk
Date: Mon, 23 Mar 2009 21:32:35 +0100 [thread overview]
Message-ID: <1237840355.24918.80.camel@twins> (raw)
In-Reply-To: <20090323202831.GC19208@bombadil.infradead.org>
On Mon, 2009-03-23 at 16:28 -0400, Kyle McMartin wrote:
> On Mon, Mar 23, 2009 at 09:20:54PM +0100, Ingo Molnar wrote:
> >
> > Please report it in that case and get us to increase the limit.
> >
>
> https://bugzilla.redhat.com/show_bug.cgi?id=489563
>
> Although I don't really see how this can be particularly fixed, since
> any workload that allocates a struct with a lock, initializes, and then
> eventually frees it a whole bunch of times will run out of lock_lists
> won't it?
Not if the lock init site doesn't change. Modules are the big exception,
cycling modules will run you out of lockdep space..
next prev parent reply other threads:[~2009-03-23 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 20:16 [PATCH] degrade severity of lockdep printk Kyle McMartin
2009-03-23 20:20 ` Ingo Molnar
2009-03-23 20:28 ` Kyle McMartin
2009-03-23 20:32 ` Peter Zijlstra [this message]
2009-03-23 20:39 ` Kyle McMartin
2009-03-23 21:12 ` Peter Zijlstra
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=1237840355.24918.80.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.