linux-um archives
 help / color / mirror / Atom feed
From: "Karol Swietlicki" <magotari@gmail.com>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: Jeff Dike <jdike@addtoit.com>, lanas <lanas@securenet.net>,
	User-mode Linux Kernel Development
	<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [uml-user] 64 bit host ?
Date: Fri, 14 Dec 2007 00:13:15 +0100	[thread overview]
Message-ID: <ea9232d10712131513l65d1a2adh1a85fba97fcda114@mail.gmail.com> (raw)
In-Reply-To: <47617E3A.2000409@nagafix.co.uk>

On 13/12/2007, Antoine Martin <antoine@nagafix.co.uk> wrote:

I follow only one list, uml-devel, so my reply is only based only on
the context that I have from this mail.

> lanas wrote:
> >>> Even then, I'm surely missing something.  The Fedora Core x86_64
> >>> binary is a mere 2 MB.  Shouldn't be a UML-patched kernel about the
> >>> same size ?

It is. In a way.
karol@BlackBox ~/expe $ du linux
22056   linux
karol@BlackBox ~/expe $ strip linux
karol@BlackBox ~/expe $ du linux
1868    linux

> >> Hmmm, not sure.
> >> Looks like the debug info is big indeed.
> >> The config files are available, so you should be able to figure out
> >> what makes it so fat. (frame-pointers?)

Not at all. Actually, as far as I know it is the lack of frame
pointers that makes the code bigger. Either way, it would never make
it bloat extremely.

> > On the other hand, I downloaded today the source code of kernel
> > 2.6.23-something and it was about 45 MB all in all.  Hard to imagine
> > that a compiled kernel would be of the same size, no ?
> Hah, yes. thinking about it, 45MB is a tad excessive!

Not really. The debug information is really plentiful.
Add in a few libraries with static compiling and you have a
monster-sized kernel on your hands.

> Antoine

Karol Swietlicki

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2007-12-13 23:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071207182146.2b6f5176@mistral.stie>
     [not found] ` <20071208040335.GA21495@c2.user-mode-linux.org>
     [not found]   ` <20071209212731.24bd6f01@mistral.stie>
     [not found]     ` <475DB98D.10001@nagafix.co.uk>
     [not found]       ` <20071210193441.1161c8ce@mistral.stie>
     [not found]         ` <475EDFA7.8020204@nagafix.co.uk>
     [not found]           ` <20071211195413.53b122d6@mistral.stie>
2007-12-13 18:47             ` [uml-devel] [uml-user] 64 bit host ? Antoine Martin
2007-12-13 23:13               ` Karol Swietlicki [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=ea9232d10712131513l65d1a2adh1a85fba97fcda114@mail.gmail.com \
    --to=magotari@gmail.com \
    --cc=antoine@nagafix.co.uk \
    --cc=jdike@addtoit.com \
    --cc=lanas@securenet.net \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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