public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Cherry <cherry@osdl.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Matt Mackall <mpm@selenic.com>, Adrian Bunk <bunk@fs.tum.de>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Bloat report 2.6.3 -> 2.6.4
Date: 14 Mar 2004 13:03:18 -0800	[thread overview]
Message-ID: <1079298197.3889.41.camel@lightning> (raw)
In-Reply-To: <20040313221741.GA1998@mars.ravnborg.org>

On Sat, 2004-03-13 at 14:17, Sam Ravnborg wrote:
> On Sat, Mar 13, 2004 at 11:33:32AM -0600, Matt Mackall wrote:
> > But I think it's fair to say that new features that are on by default
> > are in fact bloat in some sense.
> 
> You cannot do any metric based on defconfig, since per. definition defconfig is what
> suits Linus's current i386 PC best.
> If you really want to do a proper metric do something like the follwoing:
> 
> make allnoconfig
> Use some sed/awk magic to enable the options you are interested in
> - Networking
> - procfs?
> - ext2
> - One net driver
> - A bit more which make sense
> make oldconfig
> 
> This should result in a reliable config for code metrics.
> You just have to inspect that noone of your manually added options
> are no longer recognized (grep for warnings in output).
> 
> If you get this working it would be nice to see the evolution starting from 2.6.1 and
> onwards in line with John Cherrys compile stats.

I would be glad to add bloat stats to the existing compile statistics. 
However, as has been mentioned, the default config options (defconfig,
allyesconfig, and allmodconfig) change over time.  The value in the
bloat statistics would be up to the developer who could interpret these
stats relative to the current default configs.

> 
> 	Sam
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  parent reply	other threads:[~2004-03-14 21:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 20:44 Bloat report 2.6.3 -> 2.6.4 Matt Mackall
2004-03-12 23:22 ` Andrew Morton
2004-03-12 23:53   ` Matt Mackall
2004-03-13 17:08     ` Adrian Bunk
2004-03-13 17:33       ` Matt Mackall
2004-03-13 17:57         ` Adrian Bunk
2004-03-13 23:59           ` Matt Mackall
2004-03-14  0:32             ` Adrian Bunk
2004-03-14  0:57               ` Matt Mackall
2004-03-22 22:51                 ` Mike Fedyk
2004-03-24 17:22           ` Tim Bird
2004-03-13 22:17         ` Sam Ravnborg
2004-03-14  0:15           ` Matt Mackall
2004-03-14 21:03           ` John Cherry [this message]
2004-03-13 23:34     ` Horst von Brand

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=1079298197.3889.41.camel@lightning \
    --to=cherry@osdl.org \
    --cc=akpm@osdl.org \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=sam@ravnborg.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