Hi Karen,
Karen Tung wrote: > Jan Damborsky wrote: [...] >> >> [1] Specify nbpi in DC manifests. >> Looking at DC manifest, there is already section <boot_archive> >> which is used to set boot archive parameters - e.g. >> compression type (<compression>) or padding (<size_pad_mb>). >> We could add support for nbpi. >> >> [2] Work out algorithm which would automatically calculate nbpi >> during process of creating boot archive. >> For instance, nbpi might be function of ramdisk size and >> number of inodes: >> nbpi = f(size of backend file, number of required inodes) >> >> [3] ? >> >> >> I think mentioned approaches have their pros and cons, e.g. >> >> [1] >> + user can set it to the desired value >> - if size or content of boot archive changes in such a way that >> build of boot archive fails, manual intervention is required - >> nbpi has to be recalculated >> >> [2] >> + no need to calculate the value manually >> - less control - user can't set it to the desired value >> >> Please let me know what you think. > Since the nbpi is a way to tune the size of the boot archive, > I think that we should provide a way for users to > specify different values so they can try out what works best for > the problem they are solving. Agreed. > > I think we can provide both option 1 and 2 you mentioned > above. By default, have the value be calculated automatically, and > display > what value is used in the log file. If users want to try out a > different value, > they can specify the number to use in the manifest, and that number will > be used, and no automatic calculation is done for them. That is a good suggestion - thanks ! Jan
