summaryrefslogtreecommitdiffstats
path: root/scripts/lib/build_perf/report.py
diff options
context:
space:
mode:
authorJoao Marcos Costa <joaomarcos.costa@bootlin.com>2025-09-01 18:07:59 +0200
committerSteve Sakoman <steve@sakoman.com>2025-09-19 07:03:31 -0700
commit03a1a4c9565554415dc2f2ce654172a33d74e2b2 (patch)
tree3c98323956daa28e823026cd9f08e82067e42052 /scripts/lib/build_perf/report.py
parent0813376d840e05d75a844853d288e91a89e92e1e (diff)
downloadpoky-03a1a4c9565554415dc2f2ce654172a33d74e2b2.tar.gz
ref-manual/variables.rst: expand IMAGE_OVERHEAD_FACTOR glossary entry
There's a (second) overhead factor applied in images generated with Wic, and this is already documented in the .wks reference. However, the IMAGE_OVERHEAD_FACTOR entry does not mention it, and by looking at the partition sizes (e.g. with parted) one may find it confusing that they don't match with the expected rootfs size (e.g. in a scenario where the extra space is "0" and IMAGE_OVERHEAD_FACTOR="1.0"). This second overhead is already documented, though: https://docs.yoctoproject.org/ref-manual/kickstart.html#command-part-or-partition Mention the '--overhead-factor' option in the glossary entry and add a reference to the wks documentation. (From yocto-docs rev: 71a3933c609ce73ff07e5be48d9e7b03f22ef8d7) Signed-off-by: Joao Marcos Costa <joaomarcos.costa@bootlin.com> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> (cherry picked from commit b9040e20b015e9b02683ec3014e4ade5eb59d41a) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'scripts/lib/build_perf/report.py')
0 files changed, 0 insertions, 0 deletions