From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Konstantin Osipov <kostja.osipov@gmail.com>,
tarantool-patches@dev.tarantool.org, olegrok@tarantool.org
Subject: Re: [Tarantool-patches] [PATCH vshard 1/1] router: bucket_id_strcrc32 and bucket_id_mpcrc32
Date: Sat, 29 Feb 2020 18:10:10 +0100 [thread overview]
Message-ID: <e21fb74c-3040-a165-4952-371f5f8839ad@tarantool.org> (raw)
In-Reply-To: <20200227065325.GF29715@atlas>
On 27/02/2020 07:53, Konstantin Osipov wrote:
> * Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [20/02/27 09:42]:
>>> * Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [20/02/26 09:31]:
>>>> Closes #207
>>>
>>> While you're at it, is this hardware crc32?
>>
>> Yes, this is hardware, when possible. And it is in C. See crc32.c
>> files (there are two of them).
>
> I mean the entire method could be in C, including building a
> msgpack string from cdata.
But how building MessagePack is related to crc32? We will need to
do that in C anyway. Now I am doing that via msgpackffi, which is
fast enough.
So in both cases we have MessagePack building, 1 Lua C call, and
optimal crc32 calculation in C.
next prev parent reply other threads:[~2020-02-29 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 23:52 Vladislav Shpilevoy
2020-02-26 7:15 ` Oleg Babin
2020-02-27 0:22 ` Vladislav Shpilevoy
2020-02-27 10:12 ` Oleg Babin
2020-02-29 17:09 ` Vladislav Shpilevoy
2020-03-02 8:10 ` Oleg Babin
2020-03-02 21:06 ` Vladislav Shpilevoy
2020-02-26 8:20 ` Konstantin Osipov
2020-02-27 0:25 ` Vladislav Shpilevoy
2020-02-27 6:53 ` Konstantin Osipov
2020-02-29 17:10 ` Vladislav Shpilevoy [this message]
2020-03-01 16:52 ` Konstantin Osipov
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=e21fb74c-3040-a165-4952-371f5f8839ad@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=kostja.osipov@gmail.com \
--cc=olegrok@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH vshard 1/1] router: bucket_id_strcrc32 and bucket_id_mpcrc32' \
/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