From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 1/2] common: Add CCACHE variable to allow use of ccache
Date: Thu, 22 Aug 2013 17:05:22 -0700 [thread overview]
Message-ID: <5216A742.8000006@freescale.com> (raw)
In-Reply-To: <201308222136.35372.marex@denx.de>
On 08/22/2013 12:36 PM, Marek Vasut wrote:
>
> There is an env variable to configure separate ccache cache dir , so just by
> setting that. But then , when each build ends, you would need to clean it up
> somehow. It was mentioned in the discussion with the patch. You can try working
> on this some more and post a patch, then we can talk about further forging of
> this.
>
I fixed the 2nd patch and I am running MAKEALL with individual board
folder for ccache. The compiling time for the first run on my laptop is
56 minutes. The 2nd run is 23 minutes. About the same improvement if
using a big unified cache for all boards. By the way, each board cache
is about 7~8MB.
You set my expectation high. I was hoping to get 10x or more improvement.
York
next prev parent reply other threads:[~2013-08-23 0:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 17:25 [U-Boot] [PATCH 0/2] Add ccache support Marek Vasut
2013-05-20 17:25 ` [U-Boot] [PATCH 1/2] common: Add CCACHE variable to allow use of ccache Marek Vasut
2013-05-21 12:39 ` Wolfgang Denk
2013-05-21 15:04 ` Marek Vasut
2013-08-21 23:39 ` [U-Boot] [U-Boot, " York Sun
2013-08-22 2:51 ` Marek Vasut
2013-08-22 3:42 ` sun york-R58495
2013-08-22 5:02 ` Marek Vasut
2013-08-22 5:45 ` sun york-R58495
2013-08-22 5:54 ` sun york-R58495
2013-08-22 19:36 ` Marek Vasut
2013-08-23 0:05 ` York Sun [this message]
2013-08-23 3:05 ` Marek Vasut
2013-08-23 20:19 ` York Sun
2013-05-20 17:25 ` [U-Boot] [PATCH 2/2] common: Use separate dirs for each board for ccache Marek Vasut
2013-05-20 18:09 ` Marek Vasut
2013-05-21 12:45 ` Wolfgang Denk
2013-05-21 15:05 ` Marek Vasut
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=5216A742.8000006@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/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