From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/2] Ocfs2: Handle O_DIRECT writes with coherency option.
Date: Sun, 10 Oct 2010 21:43:52 +0800 [thread overview]
Message-ID: <4CB1C318.5080301@oracle.com> (raw)
In-Reply-To: <20101010105948.GT13876@mail.oracle.com>
? 2010-10-10 18:59, Joel Becker wrote:
> On Sat, Oct 09, 2010 at 07:26:42PM +0800, Tristan Ye wrote:
>> - /* concurrent O_DIRECT writes are allowed */
>> - rw_level = !direct_io;
>> + /*
>> + * concurrent O_DIRECT writes are allowed with
>> + * mount_option "coherency=buffered".
>> + */
>> + if (direct_io) {
>> + rw_level = !(osb->s_mount_opt& OCFS2_MOUNT_COHERENCY_BUFFERED);
>> + } else
>> + rw_level = !direct_io;
>> +
> I think I'd like:
>
> if (direct_io&& (osb->s_mount_opt& OCFS2_MOUNT_COHERENCY_BUFFERED))
> rw_level = 0;
> else
> rw_level = 1;
>
> It actually matches your comment much better. But since we're going to
> be using it again later, perhaps you should set 'int full_coherency =
> (osb->s_mount_opt& OCFS2_MOUNT_COHERENCY_BUFFERED)' up at the top of
> the function and then do:
>
> rw_level = (!direct_io || full_coherency)
yeah, it looks more natural.
>> ret = ocfs2_rw_lock(inode, rw_level);
>> if (ret< 0) {
>> mlog_errno(ret);
>> goto out_sems;
>> }
>>
>> + /*
>> + * O_DIRECT writes with "coherency=full" need to take EX cluster
>> + * inode_lock to guarantee coherency.
>> + */
>> + if ((direct_io)&&
>> + !(osb->s_mount_opt& OCFS2_MOUNT_COHERENCY_BUFFERED)) {
> Then this check can be:
>
> if (direct_io&& full_coherency) {
> /*
> * We need to take and drop the inode lock to force
> * other nodes to drop their caches. Buffered I/O
> * already does this in write_begin().
> */
>
>> + ret = ocfs2_inode_lock(inode, NULL, 1);
>> + if (ret< 0) {
>> + mlog_errno(ret);
>> + goto out_sems;
>> + }
>> +
>> + /*
>> + * Safe to drop the inode_lock immediately since we're just
>> + * telling other nodes to flush their cache.
>> + */
> And you don't need this comment.
I also have another concern. Do we really need the exclusive lock? I
think a PR lock should
let others to flush the cache for us.
Regards,
Tao
next prev parent reply other threads:[~2010-10-10 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 11:26 [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add a mount option "coherency=*" for O_DIRECT writes Tristan Ye
2010-10-09 11:26 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2: Handle O_DIRECT writes with coherency option Tristan Ye
2010-10-10 10:59 ` Joel Becker
2010-10-10 13:43 ` Tao Ma [this message]
2010-10-10 19:47 ` Joel Becker
2010-10-10 10:51 ` [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add a mount option "coherency=*" for O_DIRECT writes 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=4CB1C318.5080301@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).