[OE-core] [PATCH 0/7] Create ext* filesystems using debugfs

[Phil Blundell]

On Tue, 2013-02-26 at 17:24 +0800, Robert Yang wrote:
>     Before:
>     $ time bitbake core-image-minimal
>     
>     real    1m10.823s
>     user    0m37.108s
>     sys     0m15.894s
>     
>     After:
>     $ time bitbake core-image-minimal
>     
>     real    1m17.501s
>     user    0m29.304s
>     sys     0m20.731s
>     
>     # 7 seconds lost.
>   
>   - For a core-image-sato generation (IMAGE_FSTYPES="tar.bz2 ext3"):
>   
>     Before:
>     $ time bitbake core-image-sato
>     
>     real    11m10.645s
>     user    2m43.503s
>     sys     1m1.589s
>     
>     After:
>     $ time bitbake core-image-sato
>     
>     real    11m53.131s
>     user    3m18.988s
>     sys     2m8.350s
>     
>     # 43 seconds lost.
>   
> * The rootfs size changes
>   - The image size are the same by "ls -h", but different by "du -sh":
>     (core-image-sato)
>   
>     $ ls -lh BEFORE.rootfs.ext3 AFTER.rootfs.ext3 | awk '{print $5"\t"$NF}'
>     357M BEFORE.rootfs.ext3
>     357M AFTER.rootfs.ext3
>     
>     $ du -sh BEFORE.rootfs.ext3 AFTER.rootfs.ext3
>     238M    BEFORE.rootfs.ext3
>     357M    AFTER.rootfs.ext3

So, am I understanding correctly that your patch causes the rootfs
generation to take longer, and the resulting files to be bigger?  It
doesn't seem totally obvious to me that this is a good thing, and your
cover letter doesn't provide any other explanation for why the changes
are desirable.  Can you expand on the rationale for doing this?

Also, when sending patches for review, there is no point in sending a
series which adds a new file and then makes changes to it as separate
patches (in particular when the changes are just whitespace).  Please
squash those into a single patch before posting them on the list.

thanks

p.