From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Konstantin Osipov <kostja@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 1/1] swim: optimize struct swim memory layout
Date: Fri, 26 Apr 2019 22:43:06 +0300 [thread overview]
Message-ID: <97cf8cd4-b5dd-cc9b-bad1-a0d7348a4d1f@tarantool.org> (raw)
In-Reply-To: <20190426191314.GA5662@atlas>
Pushed into the master.
On 26/04/2019 22:13, Konstantin Osipov wrote:
> * Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/04/26 22:11]:
>> The same problem that occured with struct swim_member, has
>> happened with struct swim - it contains a huge structure right in
>> the middle, struct swim_task. It consumes 1.5Kb and obviously
>> splits the most accessible struct swim attributes into multiple
>> cache lines.
>
> OK to push.
>
>
> --
> Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
>
prev parent reply other threads:[~2019-04-26 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 18:49 [tarantool-patches] " Vladislav Shpilevoy
2019-04-26 19:13 ` [tarantool-patches] " Konstantin Osipov
2019-04-26 19:43 ` Vladislav Shpilevoy [this message]
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=97cf8cd4-b5dd-cc9b-bad1-a0d7348a4d1f@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 1/1] swim: optimize struct swim memory layout' \
/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