Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: "Aníbal Limón" <anibal.limon@linux.intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"Ashfield, Bruce \(Wind River\)" <bruce.ashfield@windriver.com>
Subject: Re: 2.7% build time regression caused by enabling debug/printk.scc KERNEL_FEATURE]
Date: Thu, 28 Jul 2016 22:26:59 +0300	[thread overview]
Message-ID: <20160728192659.GA31569@linux.intel.com> (raw)
In-Reply-To: <57992068.702@linux.intel.com>

On Wed, Jul 27, 2016 at 03:58:16PM -0500, Aníbal Limón wrote:
> 
> 
> On 07/27/2016 03:06 PM, Sullivan, California L wrote:
> > Adding the debug-kernel fragment to the printk fragment was probably a
> > mistake on my part. I don't see anything that requires it.
> > 
> > I'm also seeing another issue: TTY_PRINTK depends on EXPERT, which is
> > only enabled on the developer kernel by default, so you currently won't
> > be getting that option. From there, if we were to enable EXPERT,
> > DEBUG_KERNEL then gets selected automatically and we essentially end up
> > where we started and have the build time regression.
> > 
> > Stuff to think about on my end I suppose. In the mean time I +1 removing
> > the debug-kernel include from printk.scc.
> 
> I agree,
> 
> 	alimon

The fix has been merged to yocto-4.4 branch of yocto-kernel-cache:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/commit/?h=yocto-4.4&id=d3cc76c3cb20247b16c16b2367decf08b5fb90fa
And included into last kernel update:
http://lists.openembedded.org/pipermail/openembedded-core/2016-July/124466.html

With the fix applied kernel build time decreased by 22.84%:

Build Configuration:
BB_VERSION        = "1.31.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "openSUSE-13.2"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "2.1+snapshot-20160728"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta
meta-poky
meta-yocto-bsp    = "master:039f47ad197a9a53109c9f3deadd9c35e62c056d"

before the fix:
	Command being timed: "bitbake virtual/kernel"
	User time (seconds): 1367.06
	System time (seconds): 162.06
	Percent of CPU this job got: 372%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 6:50.56
	Average shared text size (kbytes): 0
	Average unshared data size (kbytes): 0
	Average stack size (kbytes): 0
	Average total size (kbytes): 0
	Maximum resident set size (kbytes): 627120
	Average resident set size (kbytes): 0
	Major (requiring I/O) page faults: 1292
	Minor (reclaiming a frame) page faults: 61097551
	Voluntary context switches: 885976
	Involuntary context switches: 715312
	Swaps: 0
	File system inputs: 1024568
	File system outputs: 13316088
	Socket messages sent: 0
	Socket messages received: 0
	Signals delivered: 0
	Page size (bytes): 4096
	Exit status: 0

after the fix:
	Command being timed: "bitbake virtual/kernel"
	User time (seconds): 1050.97
	System time (seconds): 128.84
	Percent of CPU this job got: 434%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 4:31.35
	Average shared text size (kbytes): 0
	Average unshared data size (kbytes): 0
	Average stack size (kbytes): 0
	Average total size (kbytes): 0
	Maximum resident set size (kbytes): 387148
	Average resident set size (kbytes): 0
	Major (requiring I/O) page faults: 1264
	Minor (reclaiming a frame) page faults: 52467379
	Voluntary context switches: 589830
	Involuntary context switches: 457987
	Swaps: 0
	File system inputs: 1107424
	File system outputs: 3363464
	Socket messages sent: 0
	Socket messages received: 0
	Signals delivered: 0
	Page size (bytes): 4096
	Exit status: 0


And consumed disk space decreased by 89.62%:

before the fix:
$ du -sh tmp/work/qemux86-poky-linux/linux-yocto/4.4.14+gitAUTOINC+4800a400d5_8361321fec-r0/deploy-linux-yocto/
106M

after the fix:
$ du -sh tmp/work/qemux86-poky-linux/linux-yocto/4.4.14+gitAUTOINC+86bf91f444_8361321fec-r0/deploy-linux-yocto/
11M

--
Regards,
Ed


      reply	other threads:[~2016-07-28 20:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1469620052.23580.115.camel@linuxfoundation.org>
2016-07-27 12:28 ` 2.7% build time regression caused by enabling debug/printk.scc KERNEL_FEATURE] Ed Bartosh
2016-07-27 13:06   ` Bruce Ashfield
2016-07-27 13:18     ` Ed Bartosh
2016-07-27 14:31       ` Bruce Ashfield
2016-07-27 20:06         ` Sullivan, California L
2016-07-27 20:58           ` Aníbal Limón
2016-07-28 19:26             ` Ed Bartosh [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=20160728192659.GA31569@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=anibal.limon@linux.intel.com \
    --cc=bruce.ashfield@windriver.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