Re: Fwd: [PATCH 1/1] init:add boot option "initramfs_packnum"

From: leizhen
Date: Fri Nov 21 2014 - 01:28:28 EST

On 2014/11/21 12:02, Josh Triplett wrote:
> On Fri, Nov 21, 2014 at 11:46:42AM +0800, leizhen wrote:
>> During the development phase, we usually enlarge initrd-end to reserve more
>> memory than the initfs zip exactly occupied. Then we can easily add or delete
>> files in zip package, without generate fdt again and again. But unfortunately,
>> if too many zeros followed initfs zip, it will take a long time to break the
>> loop.
>> while (!message && len) {
>> ... ...
>> if (!*buf) {
>> buf++;
>> ... ...
>> continue;
>> }
>> So, use the boot option "initramfs_packnum" to specify how many zip packages
>> in each initrd area. When the specified number of packages decompressed in one
>> area, immediately terminate the loop. Have no impact on current use by default.
> This seems like the wrong approach to me. Rather than changing Linux to
> ignore excess data in the initramfs, could you change your bootloader to
> pass the true length of the initramfs to Linux? Even if you reserve
> extra space, if you know how much data you've actually included, you
> could have your bootloader pass that information to Linux.

Yes, at release time, I will do it. But during development phase, men are lazy. Please
consider the following scenario:
We have test file1 and file2, they are all too big. We base upon file1 generated fs1.cpio.gz,
and base upon file2 generated fs2.cpio.gz. We don't put file1 and file2 into one fs package,
because the uploading is very slow on simulator or emulator. Now, we should keep fdt1 and fdt2
relate to two fs packages. If there are many test files, we should keep more fdts, it's not convenient.

But with this patch, we only need keep one fdt, and get the result the same to pass the true length.

> - Josh Triplett
> .

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at