Hi,
You mentioned earlier that Tasklet/Continuations support will be included in
2.6. Is this still the case? I don't see any mention of it in the patch
notes.
Thanks,
James
On Mon, Sep 28, 2009 at 2:29 PM, Miguel de Icaza mig...@novell.com wrote:
Hello,
Since we are getting ready for
Ah here's the problem. I didn't call yield/wait on any of the threads (and
thus store()). I fixed the problem by having every thread call yield at
least once and turning the code back to the version where one continuation
is created per step.
On Sun, Aug 30, 2009 at 12:45 AM, James Zhao jameszha
Actually, that just uses up so much memory that every 2 steps it does a gc.
On Sun, Aug 30, 2009 at 11:50 AM, James Zhao jameszha...@gmail.com wrote:
Ah here's the problem. I didn't call yield/wait on any of the threads (and
thus store()). I fixed the problem by having every thread call yield
Hi,
I'm currently working on something that uses mono 2.6's
tasklet/continuations (similar to stackless python/'eve). However, I'm
experiencing some really bizzare memory issues. I tested on Windows and
Linux.
I modified the default Mono.MicroThreads library so each microthread reuses
, Zoltan Varga var...@gmail.com wrote:
On Wed, Aug 26, 2009 at 3:11 AM, James Zhao jameszha...@gmail.com wrote:
Hi,
Thank you for that info. So that means if current stack last stack, the
stack pointer is C freed and malloced. If that's the case, then the behavior
I've been experiencing is even
Oh and here's the actual data
http://spreadsheets.google.com/pub?key=tYFncjADIjzq3rtmWF6EWdwoutput=html
On Wed, Aug 26, 2009 at 4:19 PM, James Zhao jameszha...@gmail.com wrote:
Here's a comparison of the memory (MB) and the CPU (ms) usage.
Memory Comparison - http://www.flickr.com/photos/92143
Hi,
As mentioned earlier, I'm not too good with C++ :) I just thought those two
things might be helpful for future works.
Thanks,
James
On Sun, Aug 23, 2009 at 4:10 PM, Rodrigo Kumpera kump...@gmail.com wrote:
Can you work out a patch that provided such functionality? Most of the
runtime
Hi,
Here's Mono Continuations' continuation_store (...). From looking at the
code below, it appears as though store() follows these two branches:
1. cont-saved_stack num_bytes = cont-stack_alloc_size - use the memory
directly
2. else - gc free the used memory, and create some new memory.
25, 2009 at 8:58 PM, Zoltan Varga var...@gmail.com wrote:
Hi,
mono_gc_free_fixed () is a no-op when using mono's built in GC, since
mono_gc_alloc_fixed () is implemented as a call to GC_malloc ().
Zoltan
On Wed, Aug 26, 2009 at 2:55 AM, James Zhao jameszha...@gmail.com
