From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kostja.osipov@gmail.com>
Received: from mail-lf1-f66.google.com (mail-lf1-f66.google.com
 [209.85.167.66])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by dev.tarantool.org (Postfix) with ESMTPS id 8F37046970F
 for <tarantool-patches@dev.tarantool.org>;
 Fri, 29 Nov 2019 17:51:33 +0300 (MSK)
Received: by mail-lf1-f66.google.com with SMTP id 203so22817911lfa.12
 for <tarantool-patches@dev.tarantool.org>;
 Fri, 29 Nov 2019 06:51:33 -0800 (PST)
Date: Fri, 29 Nov 2019 17:51:31 +0300
From: Konstantin Osipov <kostja.osipov@gmail.com>
Message-ID: <20191129145131.GB18043@atlas>
References: <20191128204512.19732-1-gorcunov@gmail.com>
 <20191128204512.19732-3-gorcunov@gmail.com>
 <20191129060221.GI15149@atlas> <20191129094726.GB19879@uranus>
 <20191129112203.GB7760@atlas> <20191129114205.GF19879@uranus>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20191129114205.GF19879@uranus>
Subject: Re: [Tarantool-patches] [PATCH 2/5] lua/fio: Add
	lbox_fio_push_error as a separate helper
List-Id: Tarantool development patches <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: tml <tarantool-patches@dev.tarantool.org>

* Cyrill Gorcunov <gorcunov@gmail.com> [19/11/29 16:31]:
> > Don't mix up coio and eio please. coio is
> > cooperative-wihtin-the-same-thread. eio is async via a thread
> > pool. Eio should be killed altogether now that asyncio in linux is
> > mature enough, and there is io_uring.
> 
> OK, so the longterm plans are to get rid of eio and
> use io_uring instead? I'm both hands for this kind of
> async io, except we will get a huge problems on FreeBSD/MachO
> I think (or we will have to keep eio for them).

On Mac and FreeBSD one can use aio.


-- 
Konstantin Osipov, Moscow, Russia