From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] How would you go about implementing this in Plan9?
Date: Fri, 10 Dec 2010 08:23:03 -0500 [thread overview]
Message-ID: <766a9e206b6a4134b6850efe1dc43fd4@coraid.com> (raw)
In-Reply-To: <AANLkTim6KFx3fWYzDta7bnY16aZAx8eK38KQRYo-4pTC@mail.gmail.com>
> this is trivial. On Plan9 I'm not sure how to go about this. Having separate
> processes interacting with the main one seems somewhat wrong to me (slower,
> more overhead etc).
that's single-core think. today splitting things up into multiple
processes is a good way to reduce latency or increase speed.
- erik
prev parent reply other threads:[~2010-12-10 13:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 9:34 Eugene Gorodinsky
2010-12-10 9:46 ` Lucio De Re
2010-12-10 9:58 ` hiro
2010-12-10 9:46 ` hiro
2010-12-10 10:01 ` Lucio De Re
2010-12-10 10:30 ` Charles Forsyth
2010-12-10 11:21 ` Eugene Gorodinsky
2010-12-11 1:43 ` Nathaniel W Filardo
2010-12-11 19:02 ` Eugene Gorodinsky
2010-12-10 15:52 ` David Leimbach
2010-12-10 20:01 ` Eugene Gorodinsky
2010-12-10 20:33 ` Federico G. Benavento
2010-12-11 19:01 ` Eugene Gorodinsky
2010-12-10 11:47 ` Federico G. Benavento
2010-12-10 13:23 ` erik quanstrom [this message]
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=766a9e206b6a4134b6850efe1dc43fd4@coraid.com \
--to=quanstro@labs.coraid.com \
--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).