From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3DBC0C433E0 for ; Thu, 18 Jun 2020 08:39:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1CD38214DB for ; Thu, 18 Jun 2020 08:39:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=javigon-com.20150623.gappssmtp.com header.i=@javigon-com.20150623.gappssmtp.com header.b="Jp9qjrjh" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728924AbgFRIjp (ORCPT ); Thu, 18 Jun 2020 04:39:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57632 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728706AbgFRIjo (ORCPT ); Thu, 18 Jun 2020 04:39:44 -0400 Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com [IPv6:2a00:1450:4864:20::441]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AC519C0613EE for ; Thu, 18 Jun 2020 01:39:43 -0700 (PDT) Received: by mail-wr1-x441.google.com with SMTP id r7so5142465wro.1 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=T5c3mW8R/BEyA6E1oQI8YC00LapKInytVFfGc49f5BKHuKSkXxu8Tco3fGN7y3kydR vVJH13nl1vivgNaHKhXiES+fAX9nXIyjdtgwyd2940Ij9X6vm2RrebXm1SO3qG7ZiIdV ESc1FXFgGOXcAySjKXaZGzG2SkrD2MjXLLQxM/ro111PxHophEBsCOE29xsSGwGaIdcO LyuyEg6HINggZK5zhqr+TbbqSRCiQsLDUa6VR6TUcV9SjWybudDJOLNGtbno+vqSO5k3 Qy+eAlPE62OcqQYQQcnwT/nK6Adqh5kd3hRZCWKVoX56l9TvpMRtQq3df6JDSt9COxRq p5YA== X-Gm-Message-State: AOAM533y9TagDEj/yYFmN+SYW1EZt1hsLxeT59MjF3Ejk9OwaJM+RdAS DeJoH/Rf9ot3KModnQaz8KGRpg== X-Google-Smtp-Source: ABdhPJyDJ4nqkXRrg8KN6BZdktgYlGnBwNdxZkxcf0GETyowwUFVAIHSwSrcMLTYoBfjtVs+p7hvSA== 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: io-uring-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: io-uring@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