Hi Wu,
On Fri, Sep 6, 2024 at 7:42 PM Wu Bo wrote:
>
> On Fri, Sep 06, 2024 at 06:02:42PM +0900, Juhyung Park wrote:
> > Hi Wu,
> >
> > Interesting patch-set.
> >
> > A quick test here on my daily-driver phone's data (785558 inodes) with
> > both compression and encryption disabled, copied via rs
On Fri, Sep 06, 2024 at 06:02:42PM +0900, Juhyung Park wrote:
> Hi Wu,
>
> Interesting patch-set.
>
> A quick test here on my daily-driver phone's data (785558 inodes) with
> both compression and encryption disabled, copied via rsync to 2 fresh
> f2fs partitions with and without inline tail:
> Be
Hi Wu,
Interesting patch-set.
A quick test here on my daily-driver phone's data (785558 inodes) with
both compression and encryption disabled, copied via rsync to 2 fresh
f2fs partitions with and without inline tail:
Before: 170064928KiB
After: 169249780KiB
So about 0.48% saved.
Let me know if
On Tue, Sep 03, 2024 at 09:29:30AM -0700, Eric Biggers via Linux-f2fs-devel
wrote:
> On Tue, Sep 03, 2024 at 02:54:44AM -0600, Wu Bo via Linux-f2fs-devel wrote:
> > The inode in F2FS occupies an entire 4k block. For many small files, this
> > means
> > they consume much more space than their actu
On Tue, Sep 03, 2024 at 02:54:44AM -0600, Wu Bo via Linux-f2fs-devel wrote:
> The inode in F2FS occupies an entire 4k block. For many small files, this
> means
> they consume much more space than their actual size. Therefore, there is
> significant potential to better utilize the inode block space
The inode in F2FS occupies an entire 4k block. For many small files, this means
they consume much more space than their actual size. Therefore, there is
significant potential to better utilize the inode block space.
Currently, F2FS has two features to make use of the inode block space: inline
data
