From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: avoid direct write if we fall back to buffered
Date: Fri, 23 Apr 2010 13:06:18 -0700 [thread overview]
Message-ID: <20100423200617.GA10637@mail.oracle.com> (raw)
In-Reply-To: <201004222213.51266.lidongyang@novell.com>
On Thu, Apr 22, 2010 at 10:13:51PM +0800, Li Dongyang wrote:
> another question: why do we only take PR on the rw_lock and do not allow a
> direct write extending the i_size?
The rw_lock is the cluster equivalent of the alloc_sem. We take
a PR when we intend to use the existing allocation but will not modify
the allocation. When we want to change the allocation (filling holes,
changing unwritten extents, growing i_size) we must take an EX.
Joel
--
Life's Little Instruction Book #30
"Never buy a house without a fireplace."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-04-23 20:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 7:37 [Ocfs2-devel] [PATCH] ocfs2: avoid direct write if we fall back to buffered Dong Yang Li
2010-04-10 9:37 ` Joel Becker
2010-04-10 9:48 ` Li Dongyang
2010-04-12 5:16 ` Tao Ma
2010-04-12 5:31 ` Li Dongyang
2010-04-12 6:24 ` Tao Ma
2010-04-14 2:44 ` Tao Ma
2010-04-14 5:47 ` Li Dongyang
2010-04-14 6:08 ` Tao Ma
2010-04-13 23:54 ` Joel Becker
2010-04-14 0:13 ` Tao Ma
2010-04-14 5:58 ` Li Dongyang
2010-04-14 19:20 ` Joel Becker
2010-04-22 14:13 ` Li Dongyang
2010-04-23 20:06 ` Joel Becker [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-08 7:47 Li Dongyang
2010-04-08 18:41 ` Sunil Mushran
2010-04-09 2:27 ` Li Dongyang
2010-04-09 2:38 ` Tao Ma
2010-04-09 3:00 ` Li Dongyang
2010-04-09 3:32 ` Tao Ma
2010-04-09 9:20 ` Li Dongyang
2010-04-09 17:36 ` Sunil Mushran
2010-04-09 7:58 ` Coly Li
2010-04-09 7:56 ` Tao Ma
2010-04-14 1:58 ` Joel Becker
2010-04-14 7:42 ` Li Dongyang
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=20100423200617.GA10637@mail.oracle.com \
--to=joel.becker@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).