Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1153979ybt; Thu, 18 Jun 2020 01:42:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwUYQENKoGubDYEKMBchSlyiNNMxXZeQygF2A8gNopmkCChMug31XJcXM9K4kVhBXE5xe5C X-Received: by 2002:a17:906:a250:: with SMTP id bi16mr2868201ejb.418.1592469779227; Thu, 18 Jun 2020 01:42:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592469779; cv=none; d=google.com; s=arc-20160816; b=op2Gq4Cmlx2csV2b9LDEHjo2dSvaBFP26aoQABBll1JHlPZNVy7vU34JsnQUuEQuDU tRawlLgBuN4FEwgTY+2Z8Tyn1zLC3+xAOQF12Iyx5xHfuIHl4uu+UMgexbJ/Quv5eF0G tWihxuvWDasV4FzBHkrxABPzPnCDVxKJJ5peDpUaPH984JJi/+TpKvMGGfJTckJ6eJ+n RY5ZHrKZAD0q2Q243iC6ia4fGf8fW7LQtvFdrmk/FZeC3RAb1i0/HwXB5VviHN2uHe+m tung/nWk7866oKIckoJXCTHyvhJk6HlDVODk8Cfkgb4qcei9RHOkuW30zcKmLdIY++L6 ezpw== 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:from:date:dkim-signature; bh=bfGxedb35Oy+a+SaZCiApfvdfQftE+QGRqOTHCEiwk0=; b=k+Fvdl31SaB9YVW2gHkZyaG1FWohZTryIms5DZeblmG85BbJ2EeefSaIWpkWT/P/Ba Aohas0Lz15F0XTNB5QBaBuCiyHGnYfF1KfliFv3HE4kQ8Dt8/31i7zuvHV7qy6t+rLac 7QY0n7ExDezQpLBT7xRvH1ZJvjNtg0clgS/rY7KcWgUqFLD7NAetgd2riQjxfgwMKS+c seriPaOr6iUsS8xQB7gAHS3t2sSd5bPIpDAu7sDKPDFy5SKLtFgCRV2jbH5mvUbknKyq D980wB+fvk265KA13X9gEK6PywHcfSazG4+zvLcf+dIfZSWUZ85ILOef6ND2x8jn3KCM axyQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@javigon-com.20150623.gappssmtp.com header.s=20150623 header.b=Jp9qjrjh; 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 dt2si1968705ejc.596.2020.06.18.01.42.36; Thu, 18 Jun 2020 01:42:59 -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=Jp9qjrjh; 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 S1728706AbgFRIjq (ORCPT + 99 others); Thu, 18 Jun 2020 04:39:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57630 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728699AbgFRIjo (ORCPT ); Thu, 18 Jun 2020 04:39:44 -0400 Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ABDA8C0613ED for ; Thu, 18 Jun 2020 01:39:43 -0700 (PDT) Received: by mail-wr1-x444.google.com with SMTP id t18so5116606wru.6 for ; Thu, 18 Jun 2020 01:39:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=javigon-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=bfGxedb35Oy+a+SaZCiApfvdfQftE+QGRqOTHCEiwk0=; b=Jp9qjrjhQcFj3NXFN/4Rrfme74bB0nupeKD4ZlzQWvUS7V6iRJu1jv1Sw/xuYGTK7k ej+7JPWkQcKo3Ajn043X+/+R+2UJ5jWokpn3flKm+7PyPqNh17V4WhZVxVl8UGg64Wfl yLAVVzaAY5T02u0306kGK6RI1pOm68OMgMXs1Q6bzwjTyr46pYHRf/2EDMWEUCo1eENB ah42bVn0bM6JaiFAzRuDUo0UXVHCUtYN8YRPwPB1XYEJI1AxR6UM7zrwjYxOlgOAVjlf Murw1Sff/3vLDbdD7Obz+r4KwOHNyTfSd6/UabOTjfMlsof+K6zxD5w1t/9NBrZ/jGDZ u39Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=bfGxedb35Oy+a+SaZCiApfvdfQftE+QGRqOTHCEiwk0=; b=kRnywDj1/N4lvEDyb8TY5gFRSRabbUoI4EEE262dJWGWCq6cU+/yD0ubO35UaBo7Ru lU3gO6kosyiwSZZhVOyGOt4J7gCCbehOBIYbiNkfI5VguMjWHxojwh8c+EEreR3ycefI FzQIkvTJAadecCgFtD6ZeL5vzu2oazC7x5KQ3q60eWOMm32nHKCaXIOS0mAyl4HLSiHK kxlHW/VaNS3TPu1L7ey1rfCeDr9sGt1/dra13ZYpI9fqQExTOYVMuRA8Zudza21y/gCk /m4v2/ENwQ664EgK9iwBh4LPQpe+HQuj/C0TMW/4yAk6uJUGY/MijG60HTnjOu6im113 ls5A== X-Gm-Message-State: AOAM530gScQ4w2ERxXZGXWAYHvntjBzbylHzzqSJwpE18qwETYr6aCic gbHkFYsW80YlyE2PSLCepjA+XQ== X-Received: by 2002:adf:a18b:: with SMTP id u11mr3390432wru.102.1592469582468; Thu, 18 Jun 2020 01:39:42 -0700 (PDT) Received: from localhost ([194.62.217.57]) by smtp.gmail.com with ESMTPSA id d24sm2471775wmb.45.2020.06.18.01.39.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Jun 2020 01:39:41 -0700 (PDT) Date: Thu, 18 Jun 2020 10:39:40 +0200 From: Javier =?utf-8?B?R29uesOhbGV6?= 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: <20200618083940.jzjtbfwwyyyhpnhs@mpHalley.local> References: <1592414619-5646-1-git-send-email-joshi.k@samsung.com> <20200618082740.i4sfoi54aed6sxnk@mpHalley.local> 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:32, Matias Bjørling wrote: >On 18/06/2020 10.27, Javier González wrote: >>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. > >Christoph's response points that it is not exactly clear how this >matches with the POSIX API. Yes. We will address this. > >fio support is great - but I was thinking along the lines of >applications that not only benchmark performance. fio should be part >of the supported applications, but should not be the sole reason the >API is added. Agree. It is a process with different steps. We definitely want to have the right kernel interface before pushing any changes to libraries and / or applications. These will come as the interface becomes more stable. To start with xNVMe will be leveraging this new path. A number of customers are leveraging the xNVMe API for their applications already. Thanks, Javier