From: yan cui <ccuiyyan@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [GSOC] fast kernel compile
Date: Mon, 5 May 2014 22:35:37 -0400 [thread overview]
Message-ID: <CAAVq3r=V11c4Dj6UO1L=PCL0ca9__qWBn=HViULnVabPy+9fcg@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5hxX20=euFMeHYGh__ukJvmzffro_6F7+f-Tem9UkTDzA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
Thanks Charles for the quick reply! It is really interesting.
Believe I can find more interesting things after digging deeper.
Yan
2014-05-05 22:19 GMT-04:00 Charles Forsyth <charles.forsyth@gmail.com>:
>
> On 6 May 2014 03:13, yan cui <ccuiyyan@gmail.com> wrote:
>
>> Instead of digging much into the kernel code, I post the question here.
>> Does the speed come from its good design or insufficient kernel support?
>
>
> it's a bit of both: the compiler suite is much faster; the kernel source
> is less than the size of their include files; old drivers and obsolete code
> is eventually discarded; and it would be fair to say that device support is
> more limited, certainly compared to Linux.
>
--
Think big; Dream impossible; Make it happen.
[-- Attachment #2: Type: text/html, Size: 1480 bytes --]
next prev parent reply other threads:[~2014-05-06 2:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 2:13 yan cui
2014-05-06 2:19 ` Charles Forsyth
2014-05-06 2:35 ` yan cui [this message]
2014-05-06 2:48 ` erik quanstrom
2014-05-06 8:02 ` Charles Forsyth
2014-05-06 8:38 ` arnold
2014-05-06 8:49 ` Charles Forsyth
2014-05-06 8:54 ` arnold
2014-05-06 13:34 ` erik quanstrom
2014-05-06 9:39 ` tlaronde
2014-05-06 9:52 ` tlaronde
2014-05-06 10:02 ` Charles Forsyth
2014-05-06 13:35 ` erik quanstrom
2014-05-06 15:24 ` Aram Hăvărneanu
2014-05-06 15:48 ` Oleksandr Iakovliev
2014-05-06 15:53 ` erik quanstrom
2014-05-06 17:39 ` cinap_lenrek
2014-05-06 15:51 ` Anthony Sorace
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='CAAVq3r=V11c4Dj6UO1L=PCL0ca9__qWBn=HViULnVabPy+9fcg@mail.gmail.com' \
--to=ccuiyyan@gmail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).