From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) (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 10A2F46971A for ; Wed, 4 Dec 2019 12:44:26 +0300 (MSK) Received: by mail-lf1-f50.google.com with SMTP id n25so5632074lfl.0 for ; Wed, 04 Dec 2019 01:44:26 -0800 (PST) Date: Wed, 4 Dec 2019 12:44:24 +0300 From: Cyrill Gorcunov Message-ID: <20191204094424.GJ10140@uranus> References: <20191126180503.22238-1-gorcunov@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191126180503.22238-1-gorcunov@gmail.com> Subject: Re: [Tarantool-patches] [PATCH] fio/coio: Handle partial writes List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: tml On Tue, Nov 26, 2019 at 09:05:03PM +0300, Cyrill Gorcunov wrote: > Writting less bytes than requested is perfectly fine > from OS point of view. In turn our fio.write/pwrite > api simply returns 'true' even if only a part of > a buffer has been written. > > We can't change the api without breaking backward > compatibility (otherwise we could simply return number > of bytes written, instead of current true/false sign). > > For this sake both coio_write and coio_pwrite tries > to deliver complete data in a cycle. Drop it please, there is a small typo in it. I'll rework and send v2.