Re: + initramfs-add-initramfs_preserve_mtime-kconfig-option.patch added to -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 4 May 2022 16:46:45 +0200 David Disseldorp <ddiss@xxxxxxx> wrote:

> > Benchmarks with a one million directory cpio archive extracted 20 times
> > demonstrated: mean extraction time (s) std dev INITRAMFS_PRESERVE_MTIME=y
> > 3.808 0.006 INITRAMFS_PRESERVE_MTIME unset 3.056 0.004
> 
> The benchmark table above has been collapsed, making it mostly
> incomprehensible.

Fat fingers, thanks, fixed.

> > The above extraction times were measured using ftrace (initcall_finish -
> > initcall_start) values for populate_rootfs() with initramfs_async
> > disabled.
> > 
> > [ddiss@xxxxxxx: rebase atop dir_entry.name flexible array member and drop  separate initramfs_mtime.h header]
> > Link: https://lkml.org/lkml/2008/9/3/424
> > Link: https://lkml.kernel.org/r/20220404093429.27570-4-ddiss@xxxxxxx
> > Signed-off-by: David Disseldorp <ddiss@xxxxxxx>
> > Reviewed-by: Martin Wilck <mwilck@xxxxxxxx>
> 
> The reordering of the tags above is also somewhat confusing - I added
> the [ddiss@xxxxxxx: rebase atop ...] to reflect minor changes that I
> made to the patch *after* Martin had provided his Reviewed-by tag.

Alas, I don't think anyone would interpret it that way.

I do think it would make sense to order these things chronologically,
to provide an account of who-did-what-and-when.  But I'm not aware of
that presently being a convention with subsystem teams.  Maybe I'm
wrong about that.





[Index of Archives]     [Kernel Archive]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux