From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 1E6CC2B88E for ; Mon, 3 Jun 2019 04:09:53 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aq9bb7QWuS-y for ; Mon, 3 Jun 2019 04:09:53 -0400 (EDT) Received: from smtp21.mail.ru (smtp21.mail.ru [94.100.179.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id C88EA2B6E0 for ; Mon, 3 Jun 2019 04:09:52 -0400 (EDT) From: =?utf-8?B?0JPQtdC+0YDQs9C40Lkg0JrQuNGA0LjRh9C10L3QutC+?= Subject: [tarantool-patches] Re: [PATCH v2 7/8] Enable asyncronous wal writes Date: Mon, 03 Jun 2019 11:09:44 +0300 Message-ID: <2353965.EmFdg7sWYA@home.lan> In-Reply-To: <20190531194136.GF6141@atlas> References: <3dc25e9c195d551ce27fbaf8446a80ddcfca8a07.1558598679.git.georgy@tarantool.org> <20190531194136.GF6141@atlas> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1983658.NpjMi1XLgf"; micalg="pgp-sha256"; protocol="application/pgp-signature" Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: Konstantin Osipov Cc: tarantool-patches@freelists.org --nextPart1983658.NpjMi1XLgf Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Friday, May 31, 2019 10:41:36 PM MSK Konstantin Osipov wrote: > * Georgy Kirichenko [19/05/23 11:48]: > > Allow to send a journal entry to wal without wait until the writing > > > > was finished. Two methods were introduced: > > * async_write method emits an entry to be written, returns 0 if the > > entry was successfully scheduled; > > * async_wait method waits until writing was finished and returns a > > result of journal write. > > Seems that write async and wait async are the default uses for the > journal now. Can we swap the names around, and use > journal_write/journal_wait for async methods, and > journal_write_sync for the few places that use the sync one? Accepted, thanks --nextPart1983658.NpjMi1XLgf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEFB+nbqWGnp59Rk9ZFSyY70x8X3sFAlz01cgACgkQFSyY70x8 X3uhLAf+MCbPHQAvYoSAL7vw6e6hrU8jlrcmL3HVQ9KFAK9UOGvGL/U6Zs+vtB1k 5De6yOspf0qcMq1HHFG+6QccgfGmN3t2aKvzaQZTX9fhG81KkIy1bMllRZHCFgke ATPaIY0QFihlj04D+Yxujan/7pZ/mYABoDTITHldF7dPbzX1QqB/zTOQz2JcnGZU gU4u8X01TvRBShK1UAzsMM7Vkf1MpzFsFkDPBlOWXGER0D3JrvWMmTCtMJetm4cy SkNqq3ZxYc/Ts4cVtmjxGKBVOj2wqb82G04sniNP6y/9nN8/QIk3ExUNPSoIqk7V G+UEI+uqnqgNeo6TeOaDpvQcStcfVg== =/e1U -----END PGP SIGNATURE----- --nextPart1983658.NpjMi1XLgf--