From: Jeff Layton <jlayton@poochiereds.net>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: OFD locks and deadlock detection
Date: Mon, 19 May 2014 10:28:02 -0400 [thread overview]
Message-ID: <20140519102802.16dee141@tlielax.poochiereds.net> (raw)
In-Reply-To: <537A0495.60107@gmail.com>
On Mon, 19 May 2014 15:18:13 +0200
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> wrote:
> Hi Jeff,
>
> I just happened to notice :
>
> commit 57b65325fe34ec4c917bc4e555144b4a94d9e1f7
> Author: Jeff Layton <jlayton@redhat.com>
> Date: Mon Feb 3 12:13:09 2014 -0500
>
> locks: skip deadlock detection on FL_FILE_PVT locks
>
> And then this thread:
>
> http://thread.gmane.org/gmane.linux.file-systems/81318/focus=81327
> From: Jeff Layton <jlayton <at> redhat.com>
> Subject: [PATCH v5 13/14] locks: skip deadlock detection on FL_FILE_PVT locks
> Date: 2014-01-09 14:19:46 GMT
>
> I think it's pretty important to document that. All implementations
> of traditional process-associated (.k.a. "POSIX") locks that I've ever
> come across do detect deadlocks, so it's important to note that OFD locks
> do not.
>
> I plan to add the following text to the fcntl(2) page:
>
> [[
> In the current implementation,
> no deadlock detection is performed for open file description locks.
> (This contrasts with process-associated record locks,
> for which the kernel does perform deadlock detection.)
> ]]
>
> Okay?
>
> cheers,
>
> Michael
>
>
(note: I'm no longer with Red Hat, so jlayton@redhat.com no longer works)
Sounds fine to me.
FWIW, the deadlock detection for process-associated record locks is
pretty worthless except in certain narrow circumstances.
At some point, we probably should have a discussion as to whether
deadlock detection is really something we want to keep. The current
implementation requires a global spinlock which has obvious
consequences for scalability.
Thanks,
--
Jeff Layton <jlayton@poochiereds.net>
next prev parent reply other threads:[~2014-05-19 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 13:18 Michael Kerrisk (man-pages)
2014-05-19 14:28 ` Jeff Layton [this message]
2014-05-19 18:36 ` Michael Kerrisk (man-pages)
2014-05-20 9:54 ` Jeff Layton
2014-05-20 20:22 ` Michael Kerrisk (man-pages)
2014-05-21 20:58 ` Jeff Layton
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=20140519102802.16dee141@tlielax.poochiereds.net \
--to=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mtk.manpages@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®