From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f195.google.com (mail-lj1-f195.google.com [209.85.208.195]) (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 578C546970E for ; Fri, 20 Dec 2019 10:48:50 +0300 (MSK) Received: by mail-lj1-f195.google.com with SMTP id z22so4190487ljg.1 for ; Thu, 19 Dec 2019 23:48:50 -0800 (PST) Date: Fri, 20 Dec 2019 10:48:47 +0300 From: Konstantin Osipov Message-ID: <20191220074847.GF30445@atlas> References: <20191217125420.20881-1-gorcunov@gmail.com> <20191217125420.20881-2-gorcunov@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191217125420.20881-2-gorcunov@gmail.com> Subject: Re: [Tarantool-patches] [PATCH v6 1/4] coio: Export helpers and provide coio_read_fd_timeout List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cyrill Gorcunov Cc: tml * Cyrill Gorcunov [19/12/17 15:57]: > There is no reason to hide functions. In particular > we will use coio_write_fd_timeout and coio_read_fd_timeout > for popen. AFAIU the only difference between the new function and coio_read_timeout() is that the new function works without struct coio* object, but uses coio_wait(), which creates/ destroys this object on demand. Could you provide a rationale for this? coio_wait has to call EPOLL_CTL_ADD/EPOLL_CTL_DEL on every wait, so it tripples the number of syscalls per wait. On the other hand I realize that it's not super important for popen IO, but still I don't understand *why* you need this. -- Konstantin Osipov, Moscow, Russia