On 02/25, Yunlong Song wrote:
> The benefit is much, let me give an example to make the point more clear, the
> reserved_sections for a 64G image is
> about 500M, and if the current free_sections is 600M, and the IO pattern is
> like this:
>
> Before this patch:
> time 1: node & dent * imeta
On 02/25, Yunlong Song wrote:
> The benefit is much, let me give an example to make the point more clear, the
> reserved_sections for a 64G image is
> about 500M, and if the current free_sections is 600M, and the IO pattern is
> like this:
>
> Before this patch:
> time 1: node & dent * imeta
Continue to get mailing wrong message and can not receive some of emails from
linux-f2fs-de...@lists.sourceforge.net, very strange, so send again.
The benefit is much, let me give an example to make the point more clear, the
reserved_sections for a 64G image is
about 500M, and if the current
Continue to get mailing wrong message and can not receive some of emails from
linux-f2fs-de...@lists.sourceforge.net, very strange, so send again.
The benefit is much, let me give an example to make the point more clear, the
reserved_sections for a 64G image is
about 500M, and if the current
On 02/24, Yunlong Song wrote:
> Currently, it miss the part of F2FS_DIRTY_DATA to check whether there is
> enough
> free segments for the "reserved_sections" originally set in the mkfs.f2fs. As
> a
> result, it will use the reserved_sections part to write dirty data, and has to
> do gc_more to
On 02/24, Yunlong Song wrote:
> Currently, it miss the part of F2FS_DIRTY_DATA to check whether there is
> enough
> free segments for the "reserved_sections" originally set in the mkfs.f2fs. As
> a
> result, it will use the reserved_sections part to write dirty data, and has to
> do gc_more to
Currently, it miss the part of F2FS_DIRTY_DATA to check whether there is enough
free segments for the "reserved_sections" originally set in the mkfs.f2fs. As a
result, it will use the reserved_sections part to write dirty data, and has to
do gc_more to free a lot of sections together next time.
Currently, it miss the part of F2FS_DIRTY_DATA to check whether there is enough
free segments for the "reserved_sections" originally set in the mkfs.f2fs. As a
result, it will use the reserved_sections part to write dirty data, and has to
do gc_more to free a lot of sections together next time.
8 matches
Mail list logo