[lkml]   [2009]   [Mar]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 3/3] utrace-based ftrace "process" engine, v2

On Mon, 23 Mar 2009, Frank Ch. Eigler wrote:
> > I have CONFIG_DEBUG_INFO turned off in 99.9% of my kernel builds,
> > because it slows down the kernel build times significantly: [...]
> OK, 15% longer time.

It's way more than that if you don't have tons of memory and excessive
amounts of CPU power.

> > 2)
> >
> > When the kernel build becomes IO-bound [...]
> > without: 870.36 user 292.79 system 3:32.10 elapsed 548% CPU
> > with: 929.65 user 384.55 system 8:28.70 elapsed 258% CPU
> OK, lots of network traffic.

This is the _normal_ situation for a debug info build. If it's not
network traffic (distcc), it's just disk IO. Have you tried it on a
laptop? Ingo is not the only one that turns off DEBUG_INFO in disgust.
It's totally useless for any sane kernel developer - the costs are

Adn that's totally ignoring the disk usage of multiple debug info kernels.

> Note that this backs away from earlier claims that we can make do
> without debuginfo, or that the compiler can't be trusted to build the
> stuff. We all agree it'd be nice if made it better and made a little
> less.

Gaah. I'd wish you all agreed that DEBUG_INFO is just TOTALLY UNREALISTIC.


 \ /
  Last update: 2009-03-23 21:49    [W:0.074 / U:1.732 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site