Hi, I like to avoid big changes to the core feature right before a release. So I will merge this soon for the 3.31 (or 4.0).
On Tue, 2 Feb 2016 13:43:47 +0000 Victor Orlikowski <[email protected]> wrote: > Is there hope for this patch being integrated for 3.30, or is it going to be > considered for the 3.31 cycle instead? > > I am glad to address any issues or concerns, if any are still present. > > Best, > Victor > -- > Victor J. Orlikowski <> vjo@[cs.]duke.edu > >> On Jan 31, 2016, at 9:23 AM, Victor Orlikowski <[email protected]> wrote: >> >>> On Jan 31, 2016, at 7:33 AM, FUJITA Tomonori <[email protected]> wrote: >>> >>> Why we need semaphore for getting from /putting to a queue? >> >> I discovered, in testing, that eventlet synchronized queues are broken with >> respect to synchronization. >> They have missed wakeup problems that lead to them not consuming events >> properly. >> >> The eventlet semaphore is needed, in all high activity cases, to prevent >> that. >> It provides the correct synchronization semantics and is not broken. >> >> We *may* be able to remove the semaphore in the future, if I am able to get >> the eventlet maintainers to accept a patch to fix their queue >> implementation; I say "may", because I would want to test it under load >> before removing the semaphore. >> >> Best, >> Victor >> -- >> Victor J. Orlikowski <> vjo@[cs.]duke.edu >> ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
