Hi Gang,
On 2017/11/28 16:32, Gang He wrote:
> Hi Alex,
>
>
>> Hi Gang,
>>
>> On 2017/11/28 15:38, Gang He wrote:
>>> Hi Alex,
>>>
>>>
>>
Hi Gang,
On 2017/11/28 13:33, Gang He wrote:
> Hello Alex,
>
>
>> Hi Gang,
>>
>> On 2017/11/27 17:46,
On 17/11/28 16:54, Gang He wrote:
> Hi Joseph,
>
>
>
>>
>> On 17/11/28 15:24, Gang He wrote:
>>> Hello Joseph,
>>>
>>>
>>
>>>
On 17/11/28 11:35, Gang He wrote:
> Hello Joseph,
>
>
>> Hi Gang,
>>
>> On 17/11/27 17:46, Gang He wrote:
>>> Ad
Hi Joseph,
>>>
>
> On 17/11/28 15:24, Gang He wrote:
>> Hello Joseph,
>>
>>
>
>>
>>>
>>> On 17/11/28 11:35, Gang He wrote:
Hello Joseph,
>>>
> Hi Gang,
>
> On 17/11/27 17:46, Gang He wrote:
>> Add ocfs2_overwrite_io function, which is used to judge if
On 17/11/28 15:24, Gang He wrote:
> Hello Joseph,
>
>
>
>>
>> On 17/11/28 11:35, Gang He wrote:
>>> Hello Joseph,
>>>
>>>
>>
Hi Gang,
On 17/11/27 17:46, Gang He wrote:
> Add ocfs2_overwrite_io function, which is used to judge if
> overwrite allocated blocks, oth
Hi Alex,
>>>
> Hi Gang,
>
> On 2017/11/28 15:38, Gang He wrote:
>> Hi Alex,
>>
>>
>
>>> 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 u
Hi Gang,
On 2017/11/28 15:38, Gang He wrote:
> Hi Alex,
>
>
>> 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 alloc
Hi Alex,
>>>
> 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
On 2017/11/28 13:44, Gang He wrote:
> Hi Changwei,
>
>
>> Hi,
>> Gang
>>
>> On 2017/11/27 17:48, 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.
>>>
>>
>> Can yo
Hello Joseph,
>>>
>
> On 17/11/28 11:35, Gang He wrote:
>> Hello Joseph,
>>
>>
>
>>> Hi Gang,
>>>
>>> On 17/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 alloca
On 17/11/28 11:35, Gang He wrote:
> Hello Joseph,
>
>
>> Hi Gang,
>>
>> On 17/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-b
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.
>>>
>>> Si
Hi Changwei,
>>>
> Hi,
> Gang
>
> On 2017/11/27 17:48, 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.
>>
>
> Can you elaborate how this overhead is introduced?
> Fo
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
>> ---
>> fs/ocfs2/extent_map.c | 6
>>>
> On 2017/11/28 9:52, piaojun wrote:
>> Hi Gang,
>>
>> If ocfs2_overwrite_io is only called in 'nowait' scenarios, I wonder if
>> we can discard 'int wait' just as ext4 does:
>>
>> static bool ext4_overwrite_io(struct inode *inode, loff_t pos, loff_t len);
>
> Yes, Jun has a point.
> It
Hi Jun,
>>>
> Hi Gang,
>
> If ocfs2_overwrite_io is only called in 'nowait' scenarios, I wonder if
> we can discard 'int wait' just as ext4 does:
>
> static bool ext4_overwrite_io(struct inode *inode, loff_t pos, loff_t len);
Ok, it looks most people prefer to get rid of "wait" parameter.
Tha
Hello Joseph,
>>>
> Hi Gang,
>
> On 17/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
>> ---
>> fs/ocfs2/extent_map.c | 6
Hi,
Gang
On 2017/11/27 17:48, 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.
>
Can you elaborate how this overhead is introduced?
Forgive me, I don't figure it.
Thanks,
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
> ---
> fs/ocfs2/extent_map.c | 67
> +++
On 2017/11/28 9:52, piaojun wrote:
> Hi Gang,
>
> If ocfs2_overwrite_io is only called in 'nowait' scenarios, I wonder if
> we can discard 'int wait' just as ext4 does:
>
> static bool ext4_overwrite_io(struct inode *inode, loff_t pos, loff_t len);
Yes, Jun has a point.
It seems that ocfs2_overw
Hi Gang,
If ocfs2_overwrite_io is only called in 'nowait' scenarios, I wonder if
we can discard 'int wait' just as ext4 does:
static bool ext4_overwrite_io(struct inode *inode, loff_t pos, loff_t len);
thans,
Jun
On 2017/11/27 17:46, Gang He wrote:
> Add ocfs2_overwrite_io function, which is us
Hi Gang,
On 17/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
> ---
> fs/ocfs2/extent_map.c | 67
> +
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
---
fs/ocfs2/extent_map.c | 67 +++
fs/ocfs2/extent_map.h | 3 +++
2 fil
22 matches
Mail list logo
