From: David Miller <davem@davemloft.net>
To: samuel@sortiz.org
Cc: davej@redhat.com, linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: irda rmmod lockdep trace.
Date: Tue, 13 Mar 2007 19:22:37 -0700 (PDT) [thread overview]
Message-ID: <20070313.192237.112853631.davem@davemloft.net> (raw)
In-Reply-To: <20070314005003.GA15151@sortiz.org>
From: Samuel Ortiz <samuel@sortiz.org>
Date: Wed, 14 Mar 2007 02:50:03 +0200
> On Mon, Mar 12, 2007 at 04:49:21PM -0700, David Miller wrote:
> > I would strongly caution against adding any run-time overhead just to
> > cure a false lockdep warning. Even adding a new function argument
> > is too much IMHO.
> >
> > Make the cost show up for lockdep only, perhaps by putting each
> > hashbin lock into a seperate locking class?
> Does that look better to you:
Yes, it does.:)
next prev parent reply other threads:[~2007-03-14 2:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 22:54 irda rmmod lockdep trace Dave Jones
2007-03-10 17:43 ` Samuel Ortiz
2007-03-12 0:38 ` Samuel Ortiz
2007-03-12 23:49 ` David Miller
2007-03-13 16:18 ` Samuel Ortiz
2007-03-14 0:50 ` Samuel Ortiz
2007-03-14 2:22 ` David Miller [this message]
2007-03-16 20:19 ` Samuel Ortiz
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=20070313.192237.112853631.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=samuel@sortiz.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;
as well as URLs for NNTP newsgroup(s).