On 3/12/25 21:48, Yohan Joung wrote:
> this is unnecessary when we know we are overwriting already allocated
> blocks and the overhead of starting a transaction can be significant
> especially for multithreaded workloads doing small writes.
>
> Signed-off-by: Yohan Joung
> ---
> fs/f2fs/data.c |
On 3/14/25 20:06, Yeongjin Gil wrote:
> In the case of the following call stack for an atomic file,
> FI_DIRTY_INODE is set, but FI_ATOMIC_DIRTIED is not subsequently set.
>
> f2fs_file_write_iter
> f2fs_map_blocks
> f2fs_reserve_new_blocks
> inc_valid_block_count
> __mark_inod
On 3/12/25 11:02, Chao Yu wrote:
> On 3/12/25 03:36, Jaegeuk Kim wrote:
>> On 03/11, Chao Yu wrote:
>>> On 3/4/25 09:10, Jaegeuk Kim via Linux-f2fs-devel wrote:
From: Jaegeuk Kim
This adds a fragread command in f2fs_io, which is able to measure the
read performance on fragmente
