From: David Disseldorp <ddiss@suse.de>
To: linux-kbuild@vger.kernel.org
Subject: [RFC PATCH 0/3] scripts: headers_install: avoid some reprocessing
Date: Wed, 12 Nov 2025 00:16:19 +1100 [thread overview]
Message-ID: <20251111132021.22809-1-ddiss@suse.de> (raw)
scripts/headers_install.sh is relatively inefficient: it parses/modifies
headers via unifdef and three sed invocations, with sed output
post-processed via grep in one case (user-space CONFIG_ leaks).
These patches attempt to improve efficiency by merging two sed calls
and processing user-space CONFIG_ leak filters inline.
Unfortunately my parallel / sync headers_install benchmarks didn't show
meaningful performance improvements, hence the RFC tag.
Output is unaffected. License and CONFIG leak checks have been manually
tested via error injection.
David Disseldorp (3):
scripts: headers_install: move config_leak_ignores assignment
scripts: headers_install: filter ignored configs via sed
scripts: headers_install: avoid license check fork
scripts/headers_install.sh | 85 ++++++++++++++++++--------------------
1 file changed, 40 insertions(+), 45 deletions(-)
next reply other threads:[~2025-11-11 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 13:16 David Disseldorp [this message]
2025-11-11 13:16 ` [RFC PATCH 1/3] scripts: headers_install: move config_leak_ignores assignment David Disseldorp
2025-11-11 13:16 ` [RFC PATCH 2/3] scripts: headers_install: filter ignored configs via sed David Disseldorp
2025-11-11 13:16 ` [RFC PATCH 3/3] scripts: headers_install: avoid license check fork David Disseldorp
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=20251111132021.22809-1-ddiss@suse.de \
--to=ddiss@suse.de \
--cc=linux-kbuild@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).