[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=VgA1+fT8tUxsZN4_0SfED+ENvGVtuo01OAHRGKd2eHng@mail.gmail.com>
Date: Fri, 13 Oct 2017 08:05:11 -0700
From: Doug Anderson <dianders@...omium.org>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Sam Ravnborg <sam@...nborg.org>,
Marcin Nowakowski <marcin.nowakowski@...tec.com>,
Matthias Kaehlcke <mka@...omium.org>,
Cao jin <caoj.fnst@...fujitsu.com>,
Arnd Bergmann <arnd@...db.de>,
Mark Charlebois <charlebm@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: [PATCH v2] kbuild: shrink .cache.mk when it exceeds 1000 lines
Hi,
On Fri, Oct 13, 2017 at 4:25 AM, Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:
> The cache files are only cleaned away by "make clean". If you continue
> incremental builds, the cache files will grow up little by little.
> It is not a big deal in general use cases because compiler flags do not
> change quite often.
>
> However, if you do build-test for various architectures, compilers, and
> kernel configurations, you will end up with huge cache files soon.
>
> When the cache file exceeds 1000 lines, shrink it down to 500 by "tail".
> The Least Recently Added lines are cut. (not Least Recently Used)
> I hope it will work well enough.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@...ionext.com>
> ---
>
> Changes in v2:
> - Simplify code per Douglas Anderson
>
> scripts/Kbuild.include | 6 ++++++
> 1 file changed, 6 insertions(+)
Thanks for doing this!
Reviewed-by: Douglas Anderson <dianders@...omium.org>
Powered by blists - more mailing lists