From: "Георгий Кириченко" <georgy@tarantool.org>
To: Konstantin Osipov <kostja@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 1/2] Lightweight vclock_create and vclock_copy
Date: Tue, 12 Feb 2019 22:37:17 +0300 [thread overview]
Message-ID: <3149075.a6KHynF7k3@home.lan> (raw)
In-Reply-To: <20190212192524.GB10042@chai>
[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]
On Tuesday, February 12, 2019 10:25:24 PM MSK Konstantin Osipov wrote:
> * Georgy Kirichenko <georgy@tarantool.org> [19/02/12 17:09]:
> > /**
> >
> > @@ -158,6 +159,8 @@ vclock_get(const struct vclock *vclock, uint32_t
> > replica_id)>
> > {
> >
> > if (replica_id >= VCLOCK_MAX)
> >
> > return 0;
>
> I checked the code and I there is no place which passes arbitrary
> replica id. I believe this was added to avoid access to
> uninitialized memory in case of corrupt network packet. Now that
> vclock_get() becomes a hot path, let's avoid branching by having a
> cheaper solution for this problem:
>
> /** Avoid segmentation fault in case of malformed packet. */
> replica_id &= VLCOCK_MAX - 1;
>
> > + if ((vclock->map & (1 << replica_id)) == 0)
> > + return 0;
> >
> > return vclock->lsn[replica_id];
> >
> > }
> >
> > @@ -165,6 +168,8 @@ static inline int64_t
> >
> > vclock_inc(struct vclock *vclock, uint32_t replica_id)
> > {
> >
> > /* Easier add each time than check. */
> >
> > + if ((vclock->map & (1 << replica_id)) == 0)
> > + vclock->lsn[replica_id] = 0;
> >
> > vclock->map |= 1 << replica_id;
>
> Since you added a check, please move this assignment inside the
> branch.
>
> > vclock->signature++;
> > return ++vclock->lsn[replica_id];
> >
> > @@ -173,7 +178,13 @@ vclock_inc(struct vclock *vclock, uint32_t
> > replica_id)
> >
> > static inline void
> > vclock_copy(struct vclock *dst, const struct vclock *src)
> > {
> >
> > - *dst = *src;
> > + if (src->map == 0) {
> > + dst->map = src->map;
> > + dst->signature = src->signature;
> > + return;
> > + }
>
> Why would you ever need this branch? Looks like you can safely
> delete it.
I added this because result of bit_clz_u32(src->map) is undefined in case when
src->map == 0
>
> > + unsigned int max_pos = VCLOCK_MAX - bit_clz_u32(src->map);
> > + memcpy(dst, src, offsetof(struct vclock, lsn) + sizeof(*dst->lsn) *
> > max_pos);>
> > }
>
> Apart from these minor comments the branch is looking good, thank
> you!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-12 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 14:09 [tarantool-patches] [PATCH 0/2] Reduce wal vclock handling complecity Georgy Kirichenko
2019-02-12 14:09 ` [tarantool-patches] [PATCH 1/2] Lightweight vclock_create and vclock_copy Georgy Kirichenko
2019-02-12 19:25 ` [tarantool-patches] " Konstantin Osipov
2019-02-12 19:37 ` Георгий Кириченко [this message]
2019-02-12 14:09 ` [tarantool-patches] [PATCH 2/2] Track wal vclock changes instead of copying Georgy Kirichenko
2019-02-12 19:15 ` [tarantool-patches] " Konstantin Osipov
2019-02-12 19:47 ` Георгий Кириченко
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=3149075.a6KHynF7k3@home.lan \
--to=georgy@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 1/2] Lightweight vclock_create and vclock_copy' \
/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