From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Date: Tue, 26 Feb 2019 15:54:57 +0300 From: Cyrill Gorcunov Subject: Re: [RFC v3] fiber: Increase default stack size Message-ID: <20190226125457.GP7198@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190226123456.k66j25qv57vygm6u@esperanza> To: Vladimir Davydov Cc: =?utf-8?B?0JPQtdC+0YDQs9C40Lkg0JrQuNGA0LjRh9C10L3QutC+?= , tarantool-patches@freelists.org List-ID: On Tue, Feb 26, 2019 at 03:34:56PM +0300, Vladimir Davydov wrote: > > > > If we want to scatter we should simply put marks at page bounds. > > Dirtifying somewhere inside middle of a page is useless. > > Hmm, why? Consider the example with PATH_MAX buffer. Putting dirty marks > at page boundaries doesn't guarantee any of them will get overwritten by > the buffer if only a few hundred of bytes are used. I think we should > dirty the last page or two at random intervals - this should increase > the chance that at least one mark is overwritten by any function that is > eager for the stack. Ah, I got what you mean. Look, maybe we should consider pagemap too? iirc readin pagemap should be cheap but need to read the code though, will try once time permit.