Tarantool development patches archive
 help / color / mirror / Atom feed
From: Konstantin Osipov <kostja@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@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:13:14 +0300	[thread overview]
Message-ID: <20190426191314.GA5662@atlas> (raw)
In-Reply-To: <3267e58b092d22ccfb4dd73e06ae931b2d513f0d.1556304503.git.v.shpilevoy@tarantool.org>

* 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

  reply	other threads:[~2019-04-26 19:13 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 ` Konstantin Osipov [this message]
2019-04-26 19:43   ` [tarantool-patches] " Vladislav Shpilevoy

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=20190426191314.GA5662@atlas \
    --to=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=v.shpilevoy@tarantool.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