From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Distributed Pipelines
Date: Tue, 27 Apr 2010 08:46:22 -0400 [thread overview]
Message-ID: <74bab30800fb07a2511d904bb2ea4b95@kw.quanstro.net> (raw)
In-Reply-To: <Pine.BSI.4.64.1004261828060.19994@malasada.lava.net>
On Tue Apr 27 00:31:03 EDT 2010, newsham@lava.net wrote:
> What about some mounting/binding hackery where you replace
> /dev/cons so that the original "cpu" command works?
why the resistance to il? rx is a good example of il's strengths.
in order for cpu to work, it uses 2 extra processes. rx is much
more efficient. (and 1/4 the code) great for your trusted network.
or perhaps your local supercomputer.
rx doesn't do encryption. a srx using ssl/tls would be
able to sneak a 0 write through since the record layer
should expand that into a application record with
application data length of 0.
- erik
next prev parent reply other threads:[~2010-04-27 12:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 23:56 Akshat Kumar
2010-04-26 0:40 ` Steve Simon
2010-04-26 0:50 ` Akshat Kumar
2010-04-26 5:45 ` Eric Van Hensbergen
2010-04-26 7:33 ` Akshat Kumar
2010-04-26 7:55 ` Eric Van Hensbergen
2010-04-26 20:00 ` Akshat Kumar
2010-04-26 21:20 ` erik quanstrom
2010-04-26 21:57 ` Akshat Kumar
2010-04-26 22:17 ` erik quanstrom
2010-04-27 8:48 ` Derek Fawcus
2010-04-27 4:29 ` Tim Newsham
2010-04-27 4:31 ` lucio
2010-04-27 12:04 ` erik quanstrom
2010-04-27 12:46 ` erik quanstrom [this message]
2010-05-01 18:51 ` Ryousei Takano
2010-05-01 19:40 ` David du Colombier
2010-05-03 3:19 ` Ryousei Takano
2010-05-03 18:10 ` David du Colombier
2010-05-03 20:22 ` Russ Cox
2010-05-04 15:46 ` Jorden M
2010-05-04 17:44 ` ron minnich
2010-05-04 18:16 ` erik quanstrom
2010-05-04 18:36 ` ron minnich
2010-05-04 18:50 ` erik quanstrom
2010-05-04 19:51 ` Russ Cox
2010-05-04 19:59 ` erik quanstrom
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=74bab30800fb07a2511d904bb2ea4b95@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=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).