Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: Eric Ren <zren@suse.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Any other reading about DLM?
Date: Thu, 22 Oct 2015 11:05:02 +0800	[thread overview]
Message-ID: <5628525E.5050507@suse.com> (raw)
In-Reply-To: <5627F0E0.2010203@oracle.com>

Hi Tariq and Joseph,

Thanks very much for the information!

Eric

On 10/22/15 04:09, Tariq Saeed wrote:
> Documents/filesystems/dlmfs.txt is a concise description of how to used
> dlmfs
> without the api, using only fs open/close/remove calls.
> Regards
> -Tariq
> On 10/19/2015 10:22 PM, Eric Ren wrote:
>> Hi Joseph and all,
>>
>> In order to learn about DLM, I got [1][2][3] besides source code in
>> fs/dlm and fs/ocfs2/dlm.
>> Among them, [1][2] are for fs/dlm, and [3] is for fs/ocfs2/dlm. But most
>> parts of [3] is not complete yet.
>>
>> [1] http://opendlm.sourceforge.net/cvsmirror/opendlm/docs/dlmbook_final.pdf
>> [2] http://people.redhat.com/ccaulfie/docs/rhdlmbook.pdf
>> [3] https://oss.oracle.com/~smushran/ocfs2_dlm_design_draft.pdf
>>
>> So, I'm wondering if anyone has a complete [3]? Or Any other reading
>> like docs, notes and blogs about DLM?
>> Thanks in advance;-)
>>
>> Eric
>>
>> _______________________________________________
>> Ocfs2-devel mailing list
>> Ocfs2-devel at oss.oracle.com
>> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
>

  reply	other threads:[~2015-10-22  3:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  5:22 [Ocfs2-devel] Any other reading about DLM? Eric Ren
2015-10-21  2:32 ` Joseph Qi
2015-10-21 20:09 ` Tariq Saeed
2015-10-22  3:05   ` Eric Ren [this message]
2015-10-23  6:44     ` [Ocfs2-devel] Who know the binary ocfs2_controld? Gang He

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=5628525E.5050507@suse.com \
    --to=zren@suse.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox