From: cinap_lenrek@gmx.de (cinap_lenrek at gmx.de)
Subject: [9fans] new dial, cs and dns for ipv6
Date: Thu, 17 Mar 2011 23:11:15 +0100 [thread overview]
Message-ID: <6030ca036e779c5485206f8027ec1376@gmx.de> (raw)
In-Reply-To: <de534e85a7d140f37638e0b4541dbd2f@coraid.com>
thinking about it more... all what needs to be parallelized is the
write of the connect message so no backchannel is needed except
for reporting error/success (already done with the waitmsg in
geoffs implementation).
so it looks quite doable without any shared memory.
still, might take some time to come up with a small and clean
implementation.
so what are you going todo for now geoff?
a lib9p like forker that gets filled in by libthread is kind of a
overkill. also the code would need rewriting as you cant preserve
rfork semantics with shared stacks (you need to pass a function
pointer and arguments because the child has to run on a new allocated
stack).
--
cinap
-------------- next part --------------
An embedded message was scrubbed...
From: erik quanstrom <quanstro at labs.coraid.com>
Subject: Re: [9fans] new dial, cs and dns for ipv6
Date: Thu, 17 Mar 2011 17:38:03 -0400
Size: 2561
URL: <http://mail.9fans.net/private/9fans/attachments/20110317/123b5f2d/attachment.mht>
next prev parent reply other threads:[~2011-03-17 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 19:42 geoff at plan9.bell-labs.com
2011-03-17 20:04 ` erik quanstrom
2011-03-17 20:23 ` cinap_lenrek at gmx.de
2011-03-17 20:57 ` cinap_lenrek at gmx.de
2011-03-17 20:59 ` geoff at plan9.bell-labs.com
2011-03-17 21:12 ` cinap_lenrek at gmx.de
2011-03-17 21:38 ` erik quanstrom
2011-03-17 22:11 ` cinap_lenrek at gmx.de [this message]
2011-03-18 23:20 ` cinap_lenrek at gmx.de
2011-03-18 23:39 ` 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=6030ca036e779c5485206f8027ec1376@gmx.de \
--to=cinap_lenrek@gmx.de \
/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).