Re: [PATCH] Allocate cpg_dispatch message buffer in heap instead of stack

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From Jan Friesse Mon, 22 Apr 2013 07:54:54 -0700:
> Thanks a lot for your patch. We are currently analyzing two different
> solutions:
> - libqb dispatch functions returns raw pointer to buffer (instead of
> copy). This would mean no stack needed (and maybe also little speedup
> improvement)
> - Disallow reentrant call of *_dispatch functions (so again no stack needed)
> 
> I will definitively let you know results.
> 
> Thanks again for patch.
> 
> Regards,
>   Honza

Bringing up an archived discussion from about 6 months ago (http://lists.corosync.org/pipermail/discuss/2013-April/002533.html).

What was the determination on this? I've been working on a ruby application that uses CPG, and was just bitten by this issue. Turns out ruby only allocates 512kb for the stack in threads, so cpg_dispatch can only be called on the main thread, else it segfaults.

Thanks

-Patrick
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss

[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux