From: Coly Li <coyli@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [nov 29] what is ocfs2_lock() used for ?
Date: Wed, 03 Dec 2008 00:36:27 +0800 [thread overview]
Message-ID: <4935640B.5010508@suse.de> (raw)
In-Reply-To: <49348BF5.8040004@oracle.com>
Tao Ma Wrote:
>
>
> Coly Li wrote:
>> Hi List,
>>
>> In Linus tree, I find ocfs2_lock() in fs/ocfs2/locks.c, this function
>> can not be found from sles10
>> sp2 tree. Also I don't find any other code calling ocfs2_lock().
> It is an operation in file_operations. git log fs/ocfs2/locks.c shows
> that it is added by commit 53da4939f349d4edd283b043219221ca5b78e4d4.
>
> commit 53da4939f349d4edd283b043219221ca5b78e4d4
> Author: Mark Fasheh <mfasheh@suse.com>
> Date: Mon Jul 21 14:29:16 2008 -0700
>
> ocfs2: POSIX file locks support
>
> This is actually pretty easy since fs/dlm already handles the bulk
> of the work. The Ocfs2 userspace cluster stack module already uses
> fs/dlm as the underlying lock manager, so I only had to add the right
> calls.
>
> Cluster-aware POSIX locks ("plocks") can be turned off by the same
> means at UNIX locks - mount with 'noflocks', or create a local-only
> Ocfs2 volume. Internally, the file system uses two sets of
> file_operations, depending on whether cluster aware plocks is required.
> This turns out to be easier than implementing local-only versions of
> ->lock.
>
> Signed-off-by: Mark Fasheh <mfasheh@suse.com>
Thanks for your explaining, really helpful.
--
Coly Li
SuSE PRC Labs
next prev parent reply other threads:[~2008-12-02 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 8:31 [Ocfs2-devel] [nov 29] what is ocfs2_lock() used for ? Coly Li
2008-12-02 1:14 ` Tao Ma
2008-12-02 16:36 ` Coly Li [this message]
2008-12-02 2:27 ` Sunil Mushran
2008-12-02 16:37 ` Coly Li
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=4935640B.5010508@suse.de \
--to=coyli@suse.de \
--cc=ocfs2-devel@oss.oracle.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.