From: "Lil Evil" <Lil_Evil@gmx.de>
To: Keir Fraser <keir.fraser@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: Re: XEN Hypervisor Lines Of Code
Date: Thu, 11 Sep 2008 12:48:47 +0200 [thread overview]
Message-ID: <20080911104847.47270@gmx.net> (raw)
In-Reply-To: <C4EEB07C.26F44%keir.fraser@eu.citrix.com>
>
> > Hi
> >
> > I was just wondering if anybody keeps a record of the LOC (privileged
> LOC) in
> > the XEN Hypervisor.
> > I was under the (false???) impression that the Hypervisor consists of a
> couple
> > of tens of thousand privileged LOCs.
> > I am somewhat surprised about Joanna Rutkowskas statement about the
> 300k LOC
> > in Xen 3.3.
> > Does anybody have different (same) numbers?
>
> The number has been growing. For an x86 build, if I exclude IA64 and XSM
> components (usually not built) I count about 200k LOC. If I further
> exclude
> header files (generally don't have much code in them) then I end up about
> 150k LOC.
>
> So that's a more reasonable estimate in my opinion, at about half Joanna's
> figure. Obviously this is still rather larger than historical figures for
> Xen version 1 or Xen version 2.
>
> -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
Hi
After looking at the tree, I would say that this sounds more likely.
Maybe, http://www.xen.org/xen/ deserves an updated concerning this - or the number should be removed at all to prevent confusion.
thanks
lIl
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
next prev parent reply other threads:[~2008-09-11 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 10:11 XEN Hypervisor Lines Of Code Lil Evil
2008-09-11 10:24 ` Samuel Thibault
2008-09-11 10:24 ` Keir Fraser
2008-09-11 10:48 ` Lil Evil [this message]
2008-09-11 11:07 ` Keir Fraser
2008-09-11 15:26 ` George S. Coker, II
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=20080911104847.47270@gmx.net \
--to=lil_evil@gmx.de \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.