From: Matt Pidd-Cheshire <axwrt001@yahoo.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] It's not like lightning is it ...
Date: Tue, 8 Jun 2004 16:07:10 -0700 [thread overview]
Message-ID: <40C6469E.2010703@yahoo.com> (raw)
In-Reply-To: <015d01c44da6$54eee9f0$9b7f7d50@SOMA>
boyd, rounin wrote:
> how long does it take to boot to lunix?
sure, FreeBSD takes longer than 9
> how long does it take to compile the lunix kernel?
never timed them
> tried:
>
> size 8c gcc
meaning optimisation?
sure gcc is a whopper, 8c diminutive.
default gcc switches were used to compile, but not explicitly with
-funroll-loops -fexpensive-optimizations -m686 -O3 ... et cetera.
gcc produces fat binaries and uses many tricks
but an AVL tree ain't a complex peice of code, aside from branch
optimisations and registerising pointer dereferences I see little
for the compiler to chew on.
is kfs the bottleneck? I don't know for sure, maybe there are
things I can do to tune kfs up. Perhaps naively I'm assuming
that once booted, most other things are equal. kfs doesn't seem
to use all of the unassigned RAM as a disc cache, but in this case
it wouldn't matter anyway. I realise 9 is distributed but this is
my living room setup not a lab.
if all this sounds incredibly naive, feel free to enlighten me.
<sorry, my posts are taking time to get out; so I get replies
out of sequence.>
next prev parent reply other threads:[~2004-06-08 23:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 22:12 Matt Pidd-Cheshire
2004-06-08 22:17 ` boyd, rounin
2004-06-08 23:07 ` Matt Pidd-Cheshire [this message]
2004-06-08 23:32 ` Brantley Coile
-- strict thread matches above, loose matches on Subject: below --
2004-06-09 1:09 Matt Pidd-Cheshire
2004-06-09 1:13 ` Rob Pike
2004-06-08 21:37 Matt Pidd-Cheshire
2004-06-07 22:08 ` Charles Forsyth
2004-06-08 22:43 ` Matt Pidd-Cheshire
2004-06-08 22:54 ` Geoff Collyer
2004-06-08 21:42 ` boyd, rounin
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=40C6469E.2010703@yahoo.com \
--to=axwrt001@yahoo.com \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).