From: Arjan van de Ven <arjan@infradead.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jikos@jikos.cz>, lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 0/3] Synaptics - fix lockdep warnings
Date: Thu, 14 Sep 2006 21:03:03 +0200 [thread overview]
Message-ID: <1158260584.4200.3.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <d120d5000609141156h5e06eb68k87a6fe072a701dab@mail.gmail.com>
>
> I think it is - as far as I understand the reason for not tracking
> every lock individually is just that it is too expensive to do by
> default.
that is not correct. While it certainly plays a role,
the other reason is that you can find out "class" level locking rules
(such as inode->i_mutex comes before <other lock>) for all inodes at a
time; eg no need to see every inode do this before you can find the
deadlock.
next prev parent reply other threads:[~2006-09-14 19:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 0:44 Jiri Kosina
2006-09-14 0:44 ` [PATCH 1/3] " Jiri Kosina
2006-09-14 0:44 ` [PATCH 2/3] " Jiri Kosina
2006-09-14 0:44 ` [PATCH 3/3] " Jiri Kosina
2006-09-14 2:00 ` [PATCH 0/3] " Dmitry Torokhov
2006-09-14 8:43 ` Jiri Kosina
2006-09-14 13:18 ` Dmitry Torokhov
2006-09-14 14:39 ` Jiri Kosina
2006-09-14 14:58 ` Dmitry Torokhov
2006-09-14 15:03 ` Arjan van de Ven
2006-09-14 15:08 ` Jiri Kosina
2006-09-14 15:51 ` Dmitry Torokhov
2006-09-14 16:00 ` Jiri Kosina
2006-09-14 16:18 ` Dmitry Torokhov
2006-09-14 18:48 ` Jiri Kosina
2006-09-14 18:56 ` Dmitry Torokhov
2006-09-14 19:03 ` Arjan van de Ven [this message]
2006-09-14 19:11 ` Dmitry Torokhov
2006-09-15 5:33 ` Arjan van de Ven
2006-09-15 13:20 ` Dmitry Torokhov
2006-09-15 13:38 ` Jiri Kosina
2006-09-15 13:51 ` Dmitry Torokhov
2006-09-15 13:56 ` Dmitry Torokhov
2006-09-14 19:56 ` Ingo Molnar
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=1158260584.4200.3.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®