Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1196473ybt; Thu, 18 Jun 2020 02:58:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyO0kazJ5n4ZnM+NSaoOntSe73AaN0Vcxp0GLlzB7Qd8C+M1VWFXryRvNM7cKA3rhyazegv X-Received: by 2002:a17:906:1f4f:: with SMTP id d15mr3153787ejk.206.1592474284098; Thu, 18 Jun 2020 02:58:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592474284; cv=none; d=google.com; s=arc-20160816; b=lkWEOe6a/kwECS/QLSmJ8iQSF1PLKAQvgkjXjt4Lhv32B7gp87rb12RFBg1zh+I+rM nRzEWtZdaTRxvqCkwuISzur8J6tQNIiAW4PQZmnXW02GjOjuO4hhqegAinsVpW4mIt+u vxoRk1BDsx4O4WoWiy3qbqF3JVIe8OiPyl0WG7Sc710AEbXZRluuxJiPwHplWgTgw1bv OXfPwKbEP8kAaMJnHe2i8Q4Oo1Km0KOR3cpQdm0BnQXd+YQdUIPEgCkzbw8uGJfSBQdN FaRQaCobiqLTS9nyfw8bF9k5HwGp3Cd447BPL26Smde96JHVUOHkv5l58B/Ktei+bVjM z9dA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:date:from:dkim-signature; bh=zE4oI/xjk4gPn+qKQVZsXwzGGdGfMEP73737Hdz+jyM=; b=rPY3gQxHNoua7g1dPgklgmVhxwReGA9Bq3HIgPAnoBZ5UndvXw729FixNPgXWOOLSS WTvgmFiZJVxkifhM+S+CVoyrKVHgmYgKNj5eVZaZ2zdUyQUlw+DW2H6GHc9pZj2tzqID PioeRvksZlXhgS92uIEcH+7FqrL/jnp9+qor2cew4BQkOOyuvDxa1qebZqm8npSHcpZP eXU2R+OJ5bCPQ4j53Mh6g4mrprZz3jcx1wyf00tOGVbzWTq4hA5Qkm4M940T0rfiE/UU n2PtjBvZq3acHwSyuzoJiGSg/dZ2gqFklkTXncNUM5NKJQlkPxsUlD0CmDrhgfpQBXtS nTAg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@javigon-com.20150623.gappssmtp.com header.s=20150623 header.b="Cj/5mRQV"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j15si1568686ejk.296.2020.06.18.02.57.41; Thu, 18 Jun 2020 02:58:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@javigon-com.20150623.gappssmtp.com header.s=20150623 header.b="Cj/5mRQV"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728567AbgFRI1r (ORCPT + 99 others); Thu, 18 Jun 2020 04:27:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55754 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728465AbgFRI1o (ORCPT ); Thu, 18 Jun 2020 04:27:44 -0400 Received: from mail-wm1-x344.google.com (mail-wm1-x344.google.com [IPv6:2a00:1450:4864:20::344]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 52E0FC0613EE for ; Thu, 18 Jun 2020 01:27:44 -0700 (PDT) Received: by mail-wm1-x344.google.com with SMTP id f185so4705074wmf.3 for ; Thu, 18 Jun 2020 01:27:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=javigon-com.20150623.gappssmtp.com; s=20150623; h=from:date:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=zE4oI/xjk4gPn+qKQVZsXwzGGdGfMEP73737Hdz+jyM=; b=Cj/5mRQVF5EPtKV73CeRrVMQAnPUOaupFkki1CVBBIZx0MCP5TxMZOABRWfLgMiKx5 OrvSylExR0QnjfxyulmGMFOmZ50JLI7Y2dhI7mEAANxOhD7OYltwyqPY8MyoLq6Jtoi/ XPyfWDiJPghNpSFfnB51GYw3ZxKlDGIn+dl2geBSCCc9twmRhl8k3NBf98cnG+Cr7/ZN H00YxlfJyrRH0AD89VWqfIUpmpoZI//X+cpY448HsuY0jNb4cKG3cse5gkt9h5kq7ZOK kFhfUa3vrzFsZ2JAbG2FYifin3cYU8Xvd4Y/BITy+rGZ+qgN3RwEz0LTovGyW1s9VniT 0NVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=zE4oI/xjk4gPn+qKQVZsXwzGGdGfMEP73737Hdz+jyM=; b=FbeZ0FPorbcQMUleerLv8biOqv0DIUXqGXiwzfL11TPEVRGyPXoOeMIVBrRSmlgGFf UaRn91c53blWaFWc/GM0KXdSvE+0WPwEjM7gak3pZ00zewoiABQYFKTP9t3XlCeFb3LJ /PGAGG51T6ebsnBN95MdN28yPxzYkOF09GUcuK92IpBmggusscpaWP3hP8X5zWj1IqIS xqM2aVsAtM77Fb2Z090onR4Vxowbd2G5HcW/blnP7RscIVsw74xcQaCCjUpRPE3zEIMu bZSFcig2P1fTdO59oM0bj6yV0DU5Ld90Jx0rzu1L2APZDLBbxQyQ3B9Wsqfo3PSEbKMs WyHA== X-Gm-Message-State: AOAM532GSR+CzIkhMxdcC9VYd2GEMji4GKi1AiyUMvHeqO1qWQzgXENS lBrt3+fy+nddHVhlkyd29eCDrQ== X-Received: by 2002:a1c:2602:: with SMTP id m2mr1176878wmm.50.1592468862890; Thu, 18 Jun 2020 01:27:42 -0700 (PDT) Received: from localhost ([194.62.217.57]) by smtp.gmail.com with ESMTPSA id c6sm2627442wma.15.2020.06.18.01.27.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Jun 2020 01:27:42 -0700 (PDT) From: "Javier =?utf-8?B?R29uesOhbGV6?=" X-Google-Original-From: Javier =?utf-8?B?R29uesOhbGV6?= Date: Thu, 18 Jun 2020 10:27:40 +0200 To: Matias =?utf-8?B?QmrDuHJsaW5n?= Cc: Kanchan Joshi , axboe@kernel.dk, viro@zeniv.linux.org.uk, bcrl@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-aio@kvack.org, io-uring@vger.kernel.org, linux-block@vger.kernel.org, selvakuma.s1@samsung.com, nj.shetty@samsung.com, Damien Le Moal , Keith Busch , Christoph Hellwig Subject: Re: [PATCH 0/3] zone-append support in aio and io-uring Message-ID: <20200618082740.i4sfoi54aed6sxnk@mpHalley.local> References: <1592414619-5646-1-git-send-email-joshi.k@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 18.06.2020 10:04, Matias Bjørling wrote: >On 17/06/2020 19.23, Kanchan Joshi wrote: >>This patchset enables issuing zone-append using aio and io-uring direct-io interface. >> >>For aio, this introduces opcode IOCB_CMD_ZONE_APPEND. Application uses start LBA >>of the zone to issue append. On completion 'res2' field is used to return >>zone-relative offset. >> >>For io-uring, this introduces three opcodes: IORING_OP_ZONE_APPEND/APPENDV/APPENDV_FIXED. >>Since io_uring does not have aio-like res2, cqe->flags are repurposed to return zone-relative offset > >Please provide a pointers to applications that are updated and ready >to take advantage of zone append. Good point. We are posting a RFC with fio support for append. We wanted to start the conversation here before. We can post a fork for improve the reviews in V2. > >I do not believe it's beneficial at this point to change the libaio >API, applications that would want to use this API, should anyway >switch to use io_uring. I can see why you say this, but isn't it too restrictive to directly drop libaio support? We can split the patches and merge uring first- no proble,. > >Please also note that applications and libraries that want to take >advantage of zone append, can already use the zonefs file-system, as >it will use the zone append command when applicable. Sure. There are different paths available already, which is great. We have use cases for uring and would like to enable them too. Thanks, Javier