From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] third edition, installation experiences
Date: Sat, 10 Jun 2000 14:18:38 -0400 [thread overview]
Message-ID: <200006101822.OAA18509@smtp2.fas.harvard.edu> (raw)
My cdrom is recognized (cat sdD0/ctl looks sensible), but
the data file is all zeros.
See if cdfs(4) is any better than the kernel.
Every once in a while it is.
/dev/draw seems slower than /dev/bitblt. I wonder if the difference is
from not doing runtime code generation.
Yes, that's much of it; the code already has many
special checks to handle the common cases, but
the general case is indeed slower than it ought
to be. I have a runtime code generator started (and stopped,
for the time being), but mostly as an experiment to see what
might be gained. I expect that the problems in keeping the
instruction and data caches up to date on non-x86
and non-Intel x86 chips will make it not practical,
but maybe the win will be enormous. I don't know.
Plumbing is... interesting. I normally like to have several editors
running, keeping different work in different contexts. The new system
makes that difficult, because when one editor opens a file, the
others want to open it too.
Run plumber in the window before starting the editor,
and it will be in its own ``plumbing space''
if you will.
Russ
next reply other threads:[~2000-06-10 18:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rsc@plan9.bell-labs.com>
2000-06-10 18:18 ` Russ Cox [this message]
2000-06-11 19:09 ` Scott Schwartz
2000-06-10 19:25 jmk
2000-06-11 19:12 ` Scott Schwartz
2000-06-12 10:27 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2000-06-10 18:56 presotto
2000-06-10 18:22 rob pike
2000-06-10 17:54 Scott Schwartz
2000-06-09 15:58 jmk
[not found] <200006081831.OAA25336@smtp1.fas.harvard.edu>
[not found] ` <20000608191813.8754.qmail@g.bio.cse.psu.edu>
2000-06-09 8:27 ` Fco. J. Ballesteros
2000-06-12 15:49 ` Lyndon Nerenberg
2000-06-15 9:09 ` Fco. J. Ballesteros
2000-06-15 16:58 ` Lyndon Nerenberg
2000-06-12 9:59 ` kajri jain
2000-06-08 19:18 Scott
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=200006101822.OAA18509@smtp2.fas.harvard.edu \
--to=rsc@plan9.bell-labs.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).