From: "Jérôme Pinot" <ngc891@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "Ted Ts'o" <tytso@mit.edu>
Subject: Re: Evolution of kernel size
Date: Sat, 12 Nov 2011 22:04:49 +0900 [thread overview]
Message-ID: <20111112130449.GA10821@comet.deepsky.org> (raw)
In-Reply-To: <20111111165101.GA11227@thunk.org>
On 11/11/11 11:51, Ted Ts'o wrote:
> On Thu, Nov 10, 2011 at 11:33:33PM +0900, Jérôme Pinot wrote:
> > Hi,
> >
> > I took some time to make a graph of the evolution of the size of the
> > linux kernel tar.bz2 since version 1.0 till 3.1 (297 releases).
> > It doesn't count the stable branches (2.6.x.y).
>
> The question really is what are you trying to show with the graph, and
> what do you plan to use the graph for? If it is estimating the size
> of disk space that you'll need at some point in the future, that's
> fine. If it's for entertainment value, that's fine too.
That's exactly the point :-)
> But if it's to try to make some claims about (for example) kernel
> complexity, you'd do better to measure the size of various specific
> subsystems, such as mm, core kernel, a specific file system, etc. And
> even then, the statistics can be misleading since sometimes
> refactoring to reduce complexity or removing unneeded abstraction
> layers can end up reducing the size of the subsystem, but leave it in
> a more maintainable state.
Measuring code complexity or work/cost of the source code was out of my
scope.
--
Jérôme Pinot
http://ngc891.blogdns.net/
prev parent reply other threads:[~2011-11-12 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 14:33 Evolution of kernel size Jérôme Pinot
2011-11-10 14:59 ` Nick Bowler
2011-11-10 15:15 ` Jérôme Pinot
2011-11-10 15:40 ` Nick Bowler
2011-11-10 16:19 ` Jérôme Pinot
2011-11-11 16:51 ` Ted Ts'o
2011-11-12 13:04 ` Jérôme Pinot [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=20111112130449.GA10821@comet.deepsky.org \
--to=ngc891@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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