From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 60C9826AFC for ; Tue, 26 Feb 2019 09:02:57 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4T-M7jGMLDiF for ; Tue, 26 Feb 2019 09:02:57 -0500 (EST) Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 0563526AF4 for ; Tue, 26 Feb 2019 09:02:56 -0500 (EST) Received: by mail-lj1-f182.google.com with SMTP id g80so10857473ljg.6 for ; Tue, 26 Feb 2019 06:02:56 -0800 (PST) Date: Tue, 26 Feb 2019 17:02:54 +0300 From: Cyrill Gorcunov Subject: [tarantool-patches] Re: [RFC v3] fiber: Increase default stack size Message-ID: <20190226140254.GR7198@uranus> References: <20190222201639.GA7198@uranus> <20190225145516.6fdmob3tdkft5sky@esperanza> <20190225213955.GI7198@uranus> <20190226085852.ugkqo6dz5nmjbhze@esperanza> <20190226091254.GL7198@uranus> <20190226102656.gwwy35jyaqdkci3l@esperanza> <20190226111632.GM7198@uranus> <20190226123456.k66j25qv57vygm6u@esperanza> <20190226132631.GA21937@chai> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190226132631.GA21937@chai> Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-subscribe: List-owner: List-post: List-archive: To: Konstantin Osipov Cc: tarantool-patches@freelists.org, =?utf-8?B?0JPQtdC+0YDQs9C40Lkg0JrQuNGA0LjRh9C10L3QutC+?= On Tue, Feb 26, 2019 at 04:26:31PM +0300, Konstantin Osipov wrote: > > More importantly, since stack usage/layout is usually the same in > all fibers, i.e. it depends only on particular invocation chain, > and random markers could be set at different locations at > different fibers we are almost guaranteed to spot the problem > sooner or later, moreover, more likely sooner than later. Thanks! We will see once I manage with this problem.