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 3B48E285E0 for ; Fri, 31 May 2019 15:41:40 -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 he2lgYwFbOWd for ; Fri, 31 May 2019 15:41:40 -0400 (EDT) Received: from smtp47.i.mail.ru (smtp47.i.mail.ru [94.100.177.107]) (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 EF877283DE for ; Fri, 31 May 2019 15:41:39 -0400 (EDT) Date: Fri, 31 May 2019 22:41:36 +0300 From: Konstantin Osipov Subject: [tarantool-patches] Re: [PATCH v2 7/8] Enable asyncronous wal writes Message-ID: <20190531194136.GF6141@atlas> References: <3dc25e9c195d551ce27fbaf8446a80ddcfca8a07.1558598679.git.georgy@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3dc25e9c195d551ce27fbaf8446a80ddcfca8a07.1558598679.git.georgy@tarantool.org> 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: tarantool-patches@freelists.org Cc: Georgy Kirichenko * 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? -- Konstantin Osipov, Moscow, Russia