From: jim mckie jmk@plan9.bell-labs.com
Subject: CPU server
Date: Sun, 17 Mar 1996 19:44:23 -0500 [thread overview]
Message-ID: <19960318004423.njUE9VQ91Tm52cVgT02jn82nylAaqzQYKa-pFtfulV4@z> (raw)
There are no busmastering ethernet devices in the distribution;
the soundblaster and floppy use the generic DMA routines which
do the check and provide a buffer if necessary.
However, it's unlikely - Plan 9 does not do DMA to user
memory, only to kernel buffers. The space allocated by the
kernel at boot time for dynamic allocation is probably
within the first 16Mb.
------ forwarded message follows ------
>From cse.psu.edu!9fans-outgoing-owner Sun Mar 17 16:47:00 EST 1996
Received: from colossus.cse.psu.edu by plan9; Sun Mar 17 16:47:00 EST 1996
Received: by colossus.cse.psu.edu id <78848>; Sun, 17 Mar 1996 16:39:24 -0500
Received: from galapagos.cse.psu.edu ([130.203.2.12]) by colossus.cse.psu.edu with SMTP id <78847>; Sun, 17 Mar 1996 16:39:08 -0500
Received: from localhost by galapagos.cse.psu.edu with SMTP id <12690>; Sun, 17 Mar 1996 16:37:59 -0500
To: cse.psu.edu!9fans
Subject: Re: CPU server
In-reply-to: Your message of "Sun, 17 Mar 1996 15:03:05 EST."
<96Mar17.150802est.78842@colossus.cse.psu.edu>
Date: Sun, 17 Mar 1996 16:37:44 -0500
From: Scott Schwartz <galapagos.cse.psu.edu!schwartz>
Message-Id: <96Mar17.163759est.12690@galapagos.cse.psu.edu>
Sender: cse.psu.edu!owner-9fans
Precedence: bulk
Reply-To: cse.psu.edu!9fans
"jim mckie" <jmk@plan9.bell-labs.com> writes:
| The PC fileserver code has always been aware of this, the cpuserver/terminal
| code needs some fixes which went out recently.
What about devices other than disks? If I get more ram for my
terminal, will ethernet, soundblaster, etc, break?
next reply other threads:[~1996-03-18 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-18 0:44 jim [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-03-17 21:37 Scott
1996-03-17 20:03 jim
1996-03-17 19:03 Scott
1996-03-17 12:51 forsyth
1996-03-17 1:27 Thomas
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=19960318004423.njUE9VQ91Tm52cVgT02jn82nylAaqzQYKa-pFtfulV4@z \
--to=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).