9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@gmx.de (cinap_lenrek at gmx.de)
Subject: [9fans] new dial, cs and dns for ipv6
Date: Thu, 17 Mar 2011 21:57:40 +0100	[thread overview]
Message-ID: <2c29ac8837ddce1584fdfa2f6a866f92@gmx.de> (raw)
In-Reply-To: <7e0280cb096bbd7ac1f460fb3d4a0944@gmx.de>

correction: you can't do RFMEM|RFPROC.  RFPROC alone should work as long as
your current stack is not shared between the two processes.

i see some possible ways to implement multidial() without sharing memory
between the call workers and the caller of the dial().

use the waitmsg or a pipe to signal back a successfull dial job.

the caller can preallocate a filedescriptor per worker before fanout
and the worker signals successfull dial with a empty empty exit
string. or the dialed numerical filedescriptor number is returned in the exit
string or send on a pipe.

another way would be a shared segment, but thats kind of overkill and
ugly too.

--
cinap
-------------- next part --------------
An embedded message was scrubbed...
From: cinap_lenrek at gmx.de
Subject: Re: [9fans] new dial, cs and dns for ipv6
Date: Thu, 17 Mar 2011 21:23:37 +0100
Size: 5719
URL: <http://mail.9fans.net/private/9fans/attachments/20110317/48103708/attachment.mht>


  reply	other threads:[~2011-03-17 20:57 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 [this message]
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
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=2c29ac8837ddce1584fdfa2f6a866f92@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).