<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thank you Richard,<br>
<br>
I did a couple of trials with (mp) Queues, and with a (mp) manager.<br>
<br>
In both cases, the channel is indeed available to the child
processes, but they just cant communicate.<br>
I added two examples of this in the page <a moz-do-not-send="true"
href="http://www.internike.com/mp_stackless.html">http://www.internike.com/mp_stackless.html</a><br>
<br>
Sounds logical to me, as the channel needs a little extra logic to
differentiate between pids ("who just received something on a
pending receive() ? me, or another process ?"), which is not a
problem for threads.<br>
<br>
I'll improve, comment & let you know, after checking if there is
really nothing that can be done to make it faster.<br>
Right now, on my machine, I have around 2ms across pids, compared
to around 2µs for a real stackless channel on a single pid.<br>
Slow, but hey, getting around the GIL ;-)<br>
<br>
Cheers,<br>
<br>
Nike<br>
<br>
<br>
<br>
On 03/27/2012 11:19 PM, Richard Tew wrote:
<blockquote
cite="mid:CAN=X-THGfHJG2SU-MMXxAeuq634T0oXWPQSEDawcLgDeROpwoQ@mail.gmail.com"
type="cite">I took a skim through this morning before I left the
house, and I think it generally looked fine.<br>
<br>
Channels already work across threads, is there a reason they don't
work as is in a suitable manner? If not, perhaps we ought to
consider making them do so in Stackless itself?<br>
<br>
I'll take a closer look at the code later on when I have a more
usable device than an iPad at my hands. Just as well gmail saves
drafts as safari just crashed again..<br>
<br>
Once you're happy with it, if you want to commit a version to the
Stackless examples project let me know.<br>
<br>
Cheers,<br>
<br>
Richard.<br>
<br>
On Wednesday, March 28, 2012, <<a moz-do-not-send="true"
href="mailto:stackless.nst@internike.com">stackless.nst@internike.com</a>>
wrote:<br>
> Hey there,<br>
><br>
> I have started playing with the multiprocessing package
together with stackless.<br>
> I came up with this POC implementation of the channels,
working across processes.<br>
><br>
> If any of you stackless gurus could take a quick look there:<br>
><br>
> <a moz-do-not-send="true"
href="http://www.internike.com/mp_stackless.html">http://www.internike.com/mp_stackless.html</a><br>
><br>
> and let me know if you see any serious flaw with the basic
concept, before I get too excited about it,<br>
> I'd be infinitely grateful ;-)<br>
><br>
><br>
> Nike<br>
><br>
> _______________________________________________<br>
> Stackless mailing list<br>
> <a moz-do-not-send="true"
href="mailto:Stackless@stackless.com">Stackless@stackless.com</a><br>
> <a moz-do-not-send="true"
href="http://www.stackless.com/mailman/listinfo/stackless">http://www.stackless.com/mailman/listinfo/stackless</a><br>
>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Stackless mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Stackless@stackless.com">Stackless@stackless.com</a>
<a class="moz-txt-link-freetext" href="http://www.stackless.com/mailman/listinfo/stackless">http://www.stackless.com/mailman/listinfo/stackless</a></pre>
</blockquote>
</body>
</html>