From: alex chen <alex.chen@huawei.com>
To: Gang He <ghe@suse.com>
Cc: jlbec@evilplan.org, hch@lst.de, ocfs2-devel@oss.oracle.com,
Goldwyn Rodrigues <RGoldwyn@suse.com>,
mfasheh@versity.com, linux-kernel@vger.kernel.org
Subject: [Ocfs2-devel] [PATCH 2/3] ocfs2: add ocfs2_overwrite_io function
Date: Tue, 28 Nov 2017 14:19:47 +0800 [thread overview]
Message-ID: <5A1D0003.6060605@huawei.com> (raw)
In-Reply-To: <5A1D65C4020000F90009ACE1@prv-mh.provo.novell.com>
Hi Gang,
On 2017/11/28 13:33, Gang He wrote:
> Hello Alex,
>
>
>>>>
>> Hi Gang,
>>
>> On 2017/11/27 17:46, Gang He wrote:
>>> Add ocfs2_overwrite_io function, which is used to judge if
>>> overwrite allocated blocks, otherwise, the write will bring extra
>>> block allocation overhead.
>>>
>>> Signed-off-by: Gang He <ghe@suse.com>
>>> ---
>>> fs/ocfs2/extent_map.c | 67
>> +++++++++++++++++++++++++++++++++++++++++++++++++++
>>> fs/ocfs2/extent_map.h | 3 +++
>>> 2 files changed, 70 insertions(+)
>>>
>>> diff --git a/fs/ocfs2/extent_map.c b/fs/ocfs2/extent_map.c
>>> index e4719e0..98bf325 100644
>>> --- a/fs/ocfs2/extent_map.c
>>> +++ b/fs/ocfs2/extent_map.c
>>> @@ -832,6 +832,73 @@ int ocfs2_fiemap(struct inode *inode, struct
>> fiemap_extent_info *fieinfo,
>>> return ret;
>>> }
>>>
>>> +/* Is IO overwriting allocated blocks? */
>>> +int ocfs2_overwrite_io(struct inode *inode, u64 map_start, u64 map_len,
>>> + int wait)
>>> +{
>>> + int ret = 0, is_last;
>>> + u32 mapping_end, cpos;
>>> + struct ocfs2_super *osb = OCFS2_SB(inode->i_sb);
>>> + struct buffer_head *di_bh = NULL;
>>> + struct ocfs2_extent_rec rec;
>>> +
>>> + if (wait)
>>> + ret = ocfs2_inode_lock(inode, &di_bh, 0);
>>> + else
>>> + ret = ocfs2_try_inode_lock(inode, &di_bh, 0);
>>> + if (ret)
>>> + goto out;
>>> +
>>> + if (wait)
>>> + down_read(&OCFS2_I(inode)->ip_alloc_sem);
>>> + else {
>>> + if (!down_read_trylock(&OCFS2_I(inode)->ip_alloc_sem)) {
>>> + ret = -EAGAIN;
>>> + goto out_unlock1;
>>> + }
>>> + }
>>> +
>>> + if ((OCFS2_I(inode)->ip_dyn_features & OCFS2_INLINE_DATA_FL) &&
>>> + ((map_start + map_len) <= i_size_read(inode)))
>>> + goto out_unlock2;
>>> +
>>> + cpos = map_start >> osb->s_clustersize_bits;
>>> + mapping_end = ocfs2_clusters_for_bytes(inode->i_sb,
>>> + map_start + map_len);
>>> + is_last = 0;
>>> + while (cpos < mapping_end && !is_last) {
>>> + ret = ocfs2_get_clusters_nocache(inode, di_bh, cpos,
>>> + NULL, &rec, &is_last);
>>> + if (ret) {
>>> + mlog_errno(ret);
>>> + goto out_unlock2;
>>> + }
>>> +
>>> + if (rec.e_blkno == 0ULL)
>>> + break;
>> I think here the blocks is not overwrite, because the hold is found and the
>> blocks
>> should be allocated.
> If the rec.e_blkno == NULL, this means there is a hole.
> The file hole means that these blocks are not allocated, it does not like unwritten block.
> The unwritten blocks means that these blocks are allocated, but still have not been unwritten.
>
If we break the loop when we find the hold, out of this function we will allocate the blocks in
ocfs2_file_write_iter()->..->ocfs2_direct_IO->__blockdev_direct_IO->..->ocfs2_dio_wr_get_block()
->ocfs2_write_begin_nolock. Does this violate the semantics of 'IOCB_NOWAIT';
BTW, should we consider the down_write() and ocfs2_inode_lock() in ocfs2_dio_wr_get_block() when
the flag 'IOCB_NOWAIT' is set;
>>> +
>>> + if (rec.e_flags & OCFS2_EXT_REFCOUNTED)
>>> + break;
>>> +
>>> + cpos = le32_to_cpu(rec.e_cpos) +
>>> + le16_to_cpu(rec.e_leaf_clusters);
>>> + }
>>> +
>>> + if (cpos < mapping_end)
>>> + ret = 1;
>>> +
>>> +out_unlock2:
>>
>> I think the 'out_up_read' is more readable than the 'out_unlock2' .
> Ok, I will use more readable tag here.
>>
>>> + brelse(di_bh);
>>> +
>>> + up_read(&OCFS2_I(inode)->ip_alloc_sem);
>>> +
>>> +out_unlock1:
>>
>> We should release buffer head here.
>>
>>> + ocfs2_inode_unlock(inode, 0);
>>> +
>>> +out:
>>> + return (ret ? 0 : 1);
>>> +}
>>> +
>>> int ocfs2_seek_data_hole_offset(struct file *file, loff_t *offset, int
>> whence)
>>> {
>>> struct inode *inode = file->f_mapping->host;
>>> diff --git a/fs/ocfs2/extent_map.h b/fs/ocfs2/extent_map.h
>>> index 67ea57d..fd9e86a 100644
>>> --- a/fs/ocfs2/extent_map.h
>>> +++ b/fs/ocfs2/extent_map.h
>>> @@ -53,6 +53,9 @@ int ocfs2_extent_map_get_blocks(struct inode *inode, u64
>> v_blkno, u64 *p_blkno,
>>> int ocfs2_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
>>> u64 map_start, u64 map_len);
>>>
>>> +int ocfs2_overwrite_io(struct inode *inode, u64 map_start, u64 map_len,
>>> + int wait);
>>> +
>>> int ocfs2_seek_data_hole_offset(struct file *file, loff_t *offset, int
>> origin);
>>>
>>> int ocfs2_xattr_get_clusters(struct inode *inode, u32 v_cluster,
>>>
>
>
> .
>
WARNING: multiple messages have this Message-ID (diff)
From: alex chen <alex.chen@huawei.com>
To: Gang He <ghe@suse.com>
Cc: <jlbec@evilplan.org>, <hch@lst.de>, <ocfs2-devel@oss.oracle.com>,
"Goldwyn Rodrigues" <RGoldwyn@suse.com>, <mfasheh@versity.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Ocfs2-devel] [PATCH 2/3] ocfs2: add ocfs2_overwrite_io function
Date: Tue, 28 Nov 2017 14:19:47 +0800 [thread overview]
Message-ID: <5A1D0003.6060605@huawei.com> (raw)
In-Reply-To: <5A1D65C4020000F90009ACE1@prv-mh.provo.novell.com>
Hi Gang,
On 2017/11/28 13:33, Gang He wrote:
> Hello Alex,
>
>
>>>>
>> Hi Gang,
>>
>> On 2017/11/27 17:46, Gang He wrote:
>>> Add ocfs2_overwrite_io function, which is used to judge if
>>> overwrite allocated blocks, otherwise, the write will bring extra
>>> block allocation overhead.
>>>
>>> Signed-off-by: Gang He <ghe@suse.com>
>>> ---
>>> fs/ocfs2/extent_map.c | 67
>> +++++++++++++++++++++++++++++++++++++++++++++++++++
>>> fs/ocfs2/extent_map.h | 3 +++
>>> 2 files changed, 70 insertions(+)
>>>
>>> diff --git a/fs/ocfs2/extent_map.c b/fs/ocfs2/extent_map.c
>>> index e4719e0..98bf325 100644
>>> --- a/fs/ocfs2/extent_map.c
>>> +++ b/fs/ocfs2/extent_map.c
>>> @@ -832,6 +832,73 @@ int ocfs2_fiemap(struct inode *inode, struct
>> fiemap_extent_info *fieinfo,
>>> return ret;
>>> }
>>>
>>> +/* Is IO overwriting allocated blocks? */
>>> +int ocfs2_overwrite_io(struct inode *inode, u64 map_start, u64 map_len,
>>> + int wait)
>>> +{
>>> + int ret = 0, is_last;
>>> + u32 mapping_end, cpos;
>>> + struct ocfs2_super *osb = OCFS2_SB(inode->i_sb);
>>> + struct buffer_head *di_bh = NULL;
>>> + struct ocfs2_extent_rec rec;
>>> +
>>> + if (wait)
>>> + ret = ocfs2_inode_lock(inode, &di_bh, 0);
>>> + else
>>> + ret = ocfs2_try_inode_lock(inode, &di_bh, 0);
>>> + if (ret)
>>> + goto out;
>>> +
>>> + if (wait)
>>> + down_read(&OCFS2_I(inode)->ip_alloc_sem);
>>> + else {
>>> + if (!down_read_trylock(&OCFS2_I(inode)->ip_alloc_sem)) {
>>> + ret = -EAGAIN;
>>> + goto out_unlock1;
>>> + }
>>> + }
>>> +
>>> + if ((OCFS2_I(inode)->ip_dyn_features & OCFS2_INLINE_DATA_FL) &&
>>> + ((map_start + map_len) <= i_size_read(inode)))
>>> + goto out_unlock2;
>>> +
>>> + cpos = map_start >> osb->s_clustersize_bits;
>>> + mapping_end = ocfs2_clusters_for_bytes(inode->i_sb,
>>> + map_start + map_len);
>>> + is_last = 0;
>>> + while (cpos < mapping_end && !is_last) {
>>> + ret = ocfs2_get_clusters_nocache(inode, di_bh, cpos,
>>> + NULL, &rec, &is_last);
>>> + if (ret) {
>>> + mlog_errno(ret);
>>> + goto out_unlock2;
>>> + }
>>> +
>>> + if (rec.e_blkno == 0ULL)
>>> + break;
>> I think here the blocks is not overwrite, because the hold is found and the
>> blocks
>> should be allocated.
> If the rec.e_blkno == NULL, this means there is a hole.
> The file hole means that these blocks are not allocated, it does not like unwritten block.
> The unwritten blocks means that these blocks are allocated, but still have not been unwritten.
>
If we break the loop when we find the hold, out of this function we will allocate the blocks in
ocfs2_file_write_iter()->..->ocfs2_direct_IO->__blockdev_direct_IO->..->ocfs2_dio_wr_get_block()
->ocfs2_write_begin_nolock. Does this violate the semantics of 'IOCB_NOWAIT';
BTW, should we consider the down_write() and ocfs2_inode_lock() in ocfs2_dio_wr_get_block() when
the flag 'IOCB_NOWAIT' is set;
>>> +
>>> + if (rec.e_flags & OCFS2_EXT_REFCOUNTED)
>>> + break;
>>> +
>>> + cpos = le32_to_cpu(rec.e_cpos) +
>>> + le16_to_cpu(rec.e_leaf_clusters);
>>> + }
>>> +
>>> + if (cpos < mapping_end)
>>> + ret = 1;
>>> +
>>> +out_unlock2:
>>
>> I think the 'out_up_read' is more readable than the 'out_unlock2' .
> Ok, I will use more readable tag here.
>>
>>> + brelse(di_bh);
>>> +
>>> + up_read(&OCFS2_I(inode)->ip_alloc_sem);
>>> +
>>> +out_unlock1:
>>
>> We should release buffer head here.
>>
>>> + ocfs2_inode_unlock(inode, 0);
>>> +
>>> +out:
>>> + return (ret ? 0 : 1);
>>> +}
>>> +
>>> int ocfs2_seek_data_hole_offset(struct file *file, loff_t *offset, int
>> whence)
>>> {
>>> struct inode *inode = file->f_mapping->host;
>>> diff --git a/fs/ocfs2/extent_map.h b/fs/ocfs2/extent_map.h
>>> index 67ea57d..fd9e86a 100644
>>> --- a/fs/ocfs2/extent_map.h
>>> +++ b/fs/ocfs2/extent_map.h
>>> @@ -53,6 +53,9 @@ int ocfs2_extent_map_get_blocks(struct inode *inode, u64
>> v_blkno, u64 *p_blkno,
>>> int ocfs2_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
>>> u64 map_start, u64 map_len);
>>>
>>> +int ocfs2_overwrite_io(struct inode *inode, u64 map_start, u64 map_len,
>>> + int wait);
>>> +
>>> int ocfs2_seek_data_hole_offset(struct file *file, loff_t *offset, int
>> origin);
>>>
>>> int ocfs2_xattr_get_clusters(struct inode *inode, u32 v_cluster,
>>>
>
>
> .
>
next prev parent reply other threads:[~2017-11-28 6:19 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 9:46 [Ocfs2-devel] [PATCH 0/3] ocfs2: add nowait aio support Gang He
2017-11-27 9:46 ` Gang He
2017-11-27 9:46 ` [Ocfs2-devel] [PATCH 1/3] ocfs2: add ocfs2_try_rw_lock and ocfs2_try_inode_lock Gang He
2017-11-27 9:46 ` Gang He
2017-11-28 1:32 ` [Ocfs2-devel] " piaojun
2017-11-28 1:32 ` piaojun
2017-11-28 5:05 ` Gang He
2017-11-28 5:05 ` Gang He
2017-11-28 1:52 ` Changwei Ge
2017-11-28 1:52 ` Changwei Ge
2017-11-28 5:26 ` Gang He
2017-11-28 5:26 ` Gang He
2017-11-27 9:46 ` [Ocfs2-devel] [PATCH 2/3] ocfs2: add ocfs2_overwrite_io function Gang He
2017-11-27 9:46 ` Gang He
2017-11-28 1:13 ` [Ocfs2-devel] " Joseph Qi
2017-11-28 1:13 ` Joseph Qi
2017-11-28 3:35 ` Gang He
2017-11-28 3:35 ` Gang He
2017-11-28 6:51 ` Joseph Qi
2017-11-28 6:51 ` Joseph Qi
2017-11-28 7:24 ` Gang He
2017-11-28 7:24 ` Gang He
2017-11-28 8:40 ` Joseph Qi
2017-11-28 8:40 ` Joseph Qi
2017-11-28 8:54 ` Gang He
2017-11-28 8:54 ` Gang He
2017-11-28 9:03 ` Joseph Qi
2017-11-28 9:03 ` Joseph Qi
2017-11-28 1:50 ` piaojun
2017-11-28 1:50 ` piaojun
2017-11-28 2:10 ` Changwei Ge
2017-11-28 2:10 ` Changwei Ge
2017-11-28 5:27 ` Gang He
2017-11-28 5:27 ` Gang He
2017-11-28 5:07 ` Gang He
2017-11-28 5:07 ` Gang He
2017-11-28 2:19 ` alex chen
2017-11-28 2:19 ` alex chen
2017-11-28 5:33 ` Gang He
2017-11-28 5:33 ` Gang He
2017-11-28 6:19 ` alex chen [this message]
2017-11-28 6:19 ` alex chen
2017-11-28 7:38 ` Gang He
2017-11-28 7:38 ` Gang He
2017-11-28 8:11 ` alex chen
2017-11-28 8:11 ` alex chen
2017-11-28 8:32 ` Gang He
2017-11-28 8:32 ` Gang He
2017-11-28 13:22 ` alex chen
2017-11-28 13:22 ` alex chen
2017-11-28 2:48 ` Changwei Ge
2017-11-28 2:48 ` Changwei Ge
2017-11-28 5:40 ` Gang He
2017-11-28 5:40 ` Gang He
2017-11-28 5:48 ` Changwei Ge
2017-11-28 5:48 ` Changwei Ge
2017-11-27 9:46 ` [Ocfs2-devel] [PATCH 3/3] ocfs2: nowait aio support Gang He
2017-11-27 9:46 ` Gang He
2017-11-28 2:51 ` [Ocfs2-devel] " alex chen
2017-11-28 2:51 ` alex chen
2017-11-28 5:59 ` Gang He
2017-11-28 5:59 ` 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=5A1D0003.6060605@huawei.com \
--to=alex.chen@huawei.com \
--cc=RGoldwyn@suse.com \
--cc=ghe@suse.com \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@versity.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.