Tarantool development patches archive
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "Георгий Кириченко" <georgy@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [RFC] fiber: Increase default stack size
Date: Fri, 22 Feb 2019 12:45:28 +0300	[thread overview]
Message-ID: <20190222094528.GV7198@uranus> (raw)
In-Reply-To: <1732287.KUceHh0FeD@home.lan>

On Fri, Feb 22, 2019 at 12:24:12PM +0300, Георгий Кириченко wrote:
> > 
> > I somehow fail to see how it is different from the current scheme.
> > In the patch we put single 8 16 bytes poison at 64K (well, page
> > aligned offset to be precise) and once the fiber scheduled out we
> > test it. I suspect the difference you mean is to _when_ test the poison?
> > Or you mean to poison the whole 64K?
>
> I complain only that you check poison on each fiber schedule what could be too 
> expensive - a fiber could be scheduled about million times per second.
> I think If we would check a fiber stack poison when it goes to recycle so is 
> will be a better option.

Sounds reasonable. Will take a look, thanks! Still we should take into
account that the stack of a fiber (for our regular fibers) won't exceed
1M thus will be covered by 2M pmd entry and expensive part is a cache
line refill only. Initially I thought if I could simply test for
poison just once when fiber is sched'ing out but then realised that
a task can easily wipe poison out on later sched cycles.

  reply	other threads:[~2019-02-22  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 21:26 Cyrill Gorcunov
2019-02-22  7:38 ` [tarantool-patches] " Георгий Кириченко
2019-02-22  7:46   ` Cyrill Gorcunov
2019-02-22  9:24     ` Георгий Кириченко
2019-02-22  9:45       ` Cyrill Gorcunov [this message]
2019-02-22 10:48 ` [tarantool-patches] " Alexander Turenko
2019-02-22 10:57   ` Cyrill Gorcunov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190222094528.GV7198@uranus \
    --to=gorcunov@gmail.com \
    --cc=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [RFC] fiber: Increase default stack size' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox