From: Matt Fleming <matt@readmodwrite.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>
Cc: linux-kernel@vger.kernel.org, kernel-team@cloudflare.com,
Matt Fleming <mfleming@cloudflare.com>
Subject: [PATCH] kbuild: Add KDEB_COMPRESS_LEVEL to control compression level
Date: Fri, 7 Mar 2025 15:09:40 +0000 [thread overview]
Message-ID: <20250307150940.1309703-1-matt@readmodwrite.com> (raw)
From: Matt Fleming <mfleming@cloudflare.com>
Give users more control to tradeoff compression time vs compressed size
when building debian packages with a new KDEB_COMPRESS_LEVEL option.
Here are some examples of using KDEB_COMPRESS=xz with
KDEB_COMPRESS_LEVEL=1 through to KDEB_COMPRESS_LEVEL=6 with the
bindeb-pkg target:
Level Time to compress Compressed size (bytes)
----- ---------------- -----------------------
1 0m36.771s 476909176
2 0m40.335s 474832644
3 0m43.635s 473845600
4 1m13.839s 472260012
5 1m18.657s 464442676
6 1m20.658s 464355000
Signed-off-by: Matt Fleming <mfleming@cloudflare.com>
---
scripts/package/debian/rules | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/package/debian/rules b/scripts/package/debian/rules
index ca07243bd5cd..616ecf1d4d1b 100755
--- a/scripts/package/debian/rules
+++ b/scripts/package/debian/rules
@@ -52,7 +52,7 @@ define binary
$(Q)dh_fixperms $(DH_OPTIONS)
$(Q)dh_gencontrol $(DH_OPTIONS) -- -f$(call mk-files,$@)
$(Q)dh_md5sums $(DH_OPTIONS)
- $(Q)dh_builddeb $(DH_OPTIONS) -- $(addprefix -Z,$(KDEB_COMPRESS))
+ $(Q)dh_builddeb $(DH_OPTIONS) -- $(addprefix -Z,$(KDEB_COMPRESS)) $(addprefix -z,$(KDEB_COMPRESS_LEVEL))
endef
.PHONY: $(binary-targets)
--
2.34.1
next reply other threads:[~2025-03-07 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 15:09 Matt Fleming [this message]
2025-03-13 12:38 ` [PATCH] kbuild: Add KDEB_COMPRESS_LEVEL to control compression level Matt Fleming
2025-03-14 10:06 ` Masahiro Yamada
2025-03-17 11:46 ` Matt Fleming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250307150940.1309703-1-matt@readmodwrite.com \
--to=matt@readmodwrite.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mfleming@cloudflare.com \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox