All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] Ocfs2: Add a mount option "coherency=*" to handle cluster coherency for O_DIRECT writes.
Date: Tue, 12 Oct 2010 06:09:58 +0800	[thread overview]
Message-ID: <4CB38B36.5020202@oracle.com> (raw)
In-Reply-To: <4CB38927.2070403@oracle.com>

Tao Ma wrote:
> Hi Joel,
> Joel Becker wrote:
>   
>> On Mon, Oct 11, 2010 at 04:46:39PM +0800, Tristan Ye wrote:
>>   
>>     
>>> Currently, default behavior of O_DIRECT writes was allowing
>>> concurrent writing among nodes, no cluster coherency guaranteed
>>> (no EX locks was taken), it hurts buffered reads on other nodes
>>> by reading stale data from cache.
>>>
>>> The new mount option introduce a chance to choose two different
>>> behaviors for O_DIRECT writes:
>>>
>>>     * coherency=full, as the default value, will disallow
>>>                       concurrent O_DIRECT writes by taking
>>>                       EX locks.
>>>
>>>     * coherency=buffered, allow concurrent O_DIRECT writes
>>>                           without EX lock among nodes, which
>>>                           gains high performance at risk of
>>>                           getting stale data on other nodes.
>>>
>>> Signed-off-by: Tristan Ye <tristan.ye@oracle.com>
>>>     
>>>       
>> 	This patch is now in the merge-window branch of ocfs2.git.
>>   
>>     
> I think that you agree with me that we only need to take PR lock in 
> full_coherency, but this patch
> still try the exclusive one. So do I miss something?
>   
Oh, my mistake. I read the words wrongly. Sorry for the noise.

Regards,
Tao

  reply	other threads:[~2010-10-11 22:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11  8:46 [Ocfs2-devel] [PATCH 1/1] Ocfs2: Add a mount option "coherency=*" to handle cluster coherency for O_DIRECT writes Tristan Ye
2010-10-11 21:16 ` Joel Becker
2010-10-11 22:01   ` Tao Ma
2010-10-11 22:09     ` Tao Ma [this message]
2010-10-11 22:11     ` Joel Becker

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=4CB38B36.5020202@oracle.com \
    --to=tao.ma@oracle.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 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.