From: Cyrill Gorcunov <gorcunov@gmail.com> To: Vladimir Davydov <vdavydov.dev@gmail.com> Cc: tml <tarantool-patches@freelists.org>, Alexander Turenko <alexander.turenko@tarantool.org> Subject: Re: [RFC v2] slab_arena: Enhance slab_arena_create to support madvise hints Date: Mon, 13 May 2019 13:30:32 +0300 [thread overview] Message-ID: <20190513103032.GB2544@uranus.lan> (raw) In-Reply-To: <20190513100642.h3ye4sphinkcemv4@esperanza> On Mon, May 13, 2019 at 01:06:42PM +0300, Vladimir Davydov wrote: > > > > +set(CMAKE_REQUIRED_DEFINITIONS "-D_GNU_SOURCE") > > + > > +check_symbol_exists(MAP_ANON sys/mman.h TARANTOOL_SMALL_HAVE_MAP_ANON) > > +check_symbol_exists(MAP_ANONYMOUS sys/mman.h TARANTOOL_SMALL_HAVE_MAP_ANONYMOUS) > > + > > +check_function_exists(madvise TARANTOOL_SMALL_HAS_MADVISE) > > HAS/HAVE - please be consistent in naming. OK > > +check_symbol_exists(MADV_NORMAL sys/mman.h TARANTOOL_SMALL_HAS_MADV_NORMAL) > > +check_symbol_exists(MADV_DONTDUMP sys/mman.h TARANTOOL_SMALL_HAS_MADV_DONTDUMP) > > Do we really need to check all of that? Is a check for MADV_DONTDUMP not > enough? Well, strictly speaking we should check each definition we use, because I'm not sure if MADV_NORMAL defined on other than linux environments. > > + > > +#ifdef TARANTOOL_SMALL_USE_MADVISE > > + if (slab_flags & SLAB_ARENA_DONTDUMP) > > + arena->madv_flag = MADV_DONTDUMP; > > +#endif > > May be, better store slab_flags in arena and convert them to > mmap/madvise flags when necessary? Would be one variable instead > of two. Sounds reasonable, will do. > > + > > +#ifdef TARANTOOL_SMALL_USE_MADVISE > > + if (ptr && arena->madv_flag != MADV_NORMAL) > > + madvise(ptr, arena->slab_size, arena->madv_flag); > > +#endif > > + > > I'd move this code to a helper function to avoid code duplication in > slab_arena_create/slab_map. OK > > > > +/** > > + * Backward compatible flags to be used with slab_arena_create(). > > Please elaborate the comment: explain how this backward compatibility > hack works, what it's needed for. Sure Cyrill
next prev parent reply other threads:[~2019-05-13 10:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-06 17:43 Cyrill Gorcunov 2019-05-13 10:06 ` Vladimir Davydov 2019-05-13 10:30 ` Cyrill Gorcunov [this message] 2019-05-13 11:21 ` Vladimir Davydov 2019-05-13 11:41 ` Cyrill Gorcunov 2019-05-13 11:56 ` Vladimir Davydov 2019-05-13 12:02 ` 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=20190513103032.GB2544@uranus.lan \ --to=gorcunov@gmail.com \ --cc=alexander.turenko@tarantool.org \ --cc=tarantool-patches@freelists.org \ --cc=vdavydov.dev@gmail.com \ --subject='Re: [RFC v2] slab_arena: Enhance slab_arena_create to support madvise hints' \ /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