From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: mmarek@suse.cz, akpm@linux-foundation.org, joe@perches.com,
linux-kernel@vger.kernel.org,
Michael Opdenacker <michael.opdenacker@free-electrons.com>
Subject: Re: [PATCH] scripts/checkkconfig.py: find unused Kconfig parameters
Date: Wed, 30 Oct 2013 04:14:14 +0100 [thread overview]
Message-ID: <52707986.1000200@free-electrons.com> (raw)
In-Reply-To: <20131029180619.GC3411@free.fr>
Hi Yann,
Thank you for your review!
On 10/29/2013 07:06 PM, Yann E. MORIN wrote:
> I guess all these grep spawning are what makes it slow.
>
> I wonder if it would not be possible to invert the loop (in pseudo
> Python code):
>
> for f in all_interesting_files:
> read f in memory
> for s in all_symbols:
> if symbol is in f:
> remove f from all_symbols
> break the inner-most loop
You probably meant "remove s from all_symbols", but I got it.
>
> This way:
> - you scan the tree only once
> - as soon as a symbol is matched, it is removed, thus decreasing
> the amount of checks done in further loops.
This sounds like a very good idea, thanks! I hope to have time to
implement a mix of it and Michal's proposal later this week, or at least
next week.
Thanks again,
Michael.
--
Michael Opdenacker, CEO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
+33 484 258 098
prev parent reply other threads:[~2013-10-30 3:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 5:23 [PATCH] scripts/checkkconfig.py: find unused Kconfig parameters Michael Opdenacker
2013-10-24 7:30 ` Joe Perches
2013-10-25 13:38 ` Michael Opdenacker
2013-10-25 13:45 ` Michal Marek
2013-10-30 3:07 ` Michael Opdenacker
2013-10-24 9:39 ` Michal Marek
2013-10-29 18:06 ` Yann E. MORIN
2013-10-30 3:14 ` Michael Opdenacker [this message]
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=52707986.1000200@free-electrons.com \
--to=michael.opdenacker@free-electrons.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=yann.morin.1998@free.fr \
/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