From: jmk@plan9.bell-labs.com jmk@plan9.bell-labs.com
Subject: [9fans] Plan9 commercial licenses
Date: Tue, 30 Sep 1997 15:56:42 -0400 [thread overview]
Message-ID: <19970930195642.PESfqPF4YAC5W939MiJicE5ZoALKpVCym3LGijOhvr8@z> (raw)
>Of course, might be slicker to have bitblt code in a userprocess,
>but would there a performance hit? Might not matter that much.
% ps | grep bitblt
jmk 60 1:55 0:45 1304K Read bitblt
jmk 61 0:04 0:02 1304K Read bitblt
%
next reply other threads:[~1997-09-30 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-30 19:56 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-01 7:45 elliott
1997-09-30 21:45 Eric
1997-09-30 21:19 jmk
1997-09-30 21:07 Eric
1997-09-30 20:02 Eric
1997-09-30 19:11 Scott
1997-09-30 19:09 David
1997-09-30 18:44 Eric
1997-09-30 18:20 Scott
1997-09-30 16:41 Eric
1997-09-30 16:23 Frank
1997-09-30 15:14 G.David
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=19970930195642.PESfqPF4YAC5W939MiJicE5ZoALKpVCym3LGijOhvr8@z \
--to=jmk@plan9.bell-labs.com \
/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).