From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] drawterm strangeness
Date: Tue, 24 Jun 2003 07:41:05 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0306240738590.18127-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <Pine.LNX.4.44.0306051830140.24443-100000@fbsd.cpsc.ucalgary.ca>
On Thu, 5 Jun 2003, andrey mirtchovski wrote:
> No writing or reading from disk was involved (writing same file to kfs
> instead of /dev/null or ramfs caused the transfer speed to drop down to
> 10-20mbit/s, but that's not an issue).
>
bah! i take that back! with dma on i can transfer between linux and plan9
(writing to kfs) at 90+mbits/s on a 100baseT connection...
feels like i've been asleep for three years and just woke up -- i see the
light!
i urge you to turn dma/rwm on.
next prev parent reply other threads:[~2003-06-24 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 0:48 andrey mirtchovski
2003-06-06 6:24 ` Russ Cox
2003-06-06 21:32 ` andrey mirtchovski
2003-06-24 13:41 ` andrey mirtchovski [this message]
2003-06-24 13:45 ` ron minnich
2003-06-24 13:50 ` andrey mirtchovski
2003-06-24 14:14 ` boyd, rounin
2003-06-24 17:24 ` jmk
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=Pine.LNX.4.44.0306240738590.18127-100000@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).