Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "Hart, Darren" <darren.hart@intel.com>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel: Use hardlinks for do_populate_sysroot for speed
Date: Fri, 08 Nov 2013 16:50:19 +0000	[thread overview]
Message-ID: <1383929419.2345.11.camel@ted> (raw)
In-Reply-To: <527D0A44.7020005@windriver.com>

On Fri, 2013-11-08 at 10:59 -0500, Bruce Ashfield wrote:
> On 13-11-08 10:55 AM, Richard Purdie wrote:
> > On Fri, 2013-11-08 at 10:41 -0500, Bruce Ashfield wrote:
> >> On 13-11-08 10:18 AM, Richard Purdie wrote:
> >>> The kernel tree is large and doesn't need to be copied. Override
> >>> the default sysroot handling function to use a hardlink copying
> >>> function in python.
> >>>
> >>> This commit also drops the copying of the /lib directory which
> >>> just contains the kernel modules. We never use those in the sysroot
> >>> so there is little point in carrying those around.
> >>>
> >>> For linux-yocto this takes the do_populate_sysroot time 24s -> 14s.
> >>
> >> Fantastic. One less thing for me to dig into later. I thought this
> >> was already in place, so I'm pleasantly surprised that there was a
> >> time savings to be found!
> >
> > I was somewhat surprised too.
> >
> > We still need to optimise what we install in do_install since that is
> > where significant gains can still be made.
> 
> Agreed. I started some changes in that area right after ELC-e, I'll
> try and get them out sooner rather than later.

I thought I'd share this for people's interest:

http://dan.rpsys.net/kernelbuildissue.png

Its the output from pybootchart of a bitbake core-image-sato from
scratch. I've zoomed out to put some bars in particular into
perspective.

The pink colour is linux-yocto:do_install, the cyan is
linux-yocto:do_package and the blue is linux-yocto:do_populate_sysroot.
The uncoloured bar at the bottom is linux-yocto:do_package_write_rpm.

So the final thing to build is the kernel by quite some margin, its
holding the rest of the build up.

Hopefully these patches start to improve that a bit!

Cheers,

Richard



  reply	other threads:[~2013-11-08 16:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 15:18 [PATCH] kernel: Use hardlinks for do_populate_sysroot for speed Richard Purdie
2013-11-08 15:41 ` Bruce Ashfield
2013-11-08 15:54   ` Hans Beckérus
2013-11-08 15:55   ` Richard Purdie
2013-11-08 15:59     ` Bruce Ashfield
2013-11-08 16:50       ` Richard Purdie [this message]
2013-11-08 17:23         ` Hart, Darren
2013-11-09 20:38           ` Andrea Adami
2013-11-09 22:58             ` Richard Purdie
2013-11-11  8:06               ` Hans Beckérus
2013-11-11  9:35                 ` Richard Purdie
2013-11-11  9:45                 ` Richard Purdie
2013-11-11  9:47                   ` Hans Beckérus

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=1383929419.2345.11.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.com \
    --cc=darren.hart@intel.com \
    --cc=openembedded-core@lists.openembedded.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