Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5945608ybi; Wed, 12 Jun 2019 11:09:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqx3q3+xty/9vpeODHliN5d6+zweVWX8b5uGsl7tv9TJghGXY2z3YVF+B2TAYmYthz9X75jB X-Received: by 2002:a17:902:8ec3:: with SMTP id x3mr80312464plo.340.1560362961403; Wed, 12 Jun 2019 11:09:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560362961; cv=none; d=google.com; s=arc-20160816; b=cB0OhrWFpiWSdd5WoBtm/9Rea6VOmQNOPQ5vEW0X2Uxk/QjKYQn70KrQjVDPwz+biP w8rDp7acYs1J7XnVZM3+JFSa9lj2tZuTLLTtGB6mQxWyxxlpSQK96hBE5FkO/wJ35K4P qZ804kIPUAtoUURv4DWTcnBfBkEJzTQVTTNfUhLpG20vCQ5UyGHNIAcDA1t5GCxZ7p33 evwpkxjKrO7py7S7GQCaV0sCOKq++sXc5da9I9/iWzczmPFb7p5kSsTInv+d4IpO7Q5Z uHmUvW+Wwc7XG52on41y3guCOv0poSupfemreJm3tC8FMPdyWvRO9w6sPjLbwfAwQXhI oTZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :reply-to:message-id:subject:cc:to:from:date; bh=AXuanaCqUPg0I/7WQMK4RJHfc4SrN4Mq4jozGJwJ2wA=; b=dQpjWbOjyk0RR+CQepeSsBkwQOXIIHwh95ZwKnGXbFsaHPeBO0cgQdUCBily/Y5SWe QQDvwn0gJ2/A0m/NLoQOAc7iRH5/bVRo/a3V+5S4CmudfGgojGICSXbJrnI3XhBGtK0V foR2cmxzpRcPBq203gEtzYIy8nsZo2jLIZgJwdsrrcAlbwgeP4Yc7t30pPRw/mDopFbl CS0ZtU2U84onTg1EPQ8djVzBcYBqEwPVCUv9KNCt7Ear4om8H0LElTmlGve2bmt6524Z hhcKYegAGiLXvceP6W2xV0ozK7qTBWS40fnExssRBqAnfknauSRK+ouga5KNqNQRxWbK AVSQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u126si434956pgu.117.2019.06.12.11.09.06; Wed, 12 Jun 2019 11:09:21 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387680AbfFLRuw (ORCPT + 99 others); Wed, 12 Jun 2019 13:50:52 -0400 Received: from mx2.suse.de ([195.135.220.15]:56912 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725764AbfFLRuv (ORCPT ); Wed, 12 Jun 2019 13:50:51 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 87D43AF9F; Wed, 12 Jun 2019 17:50:49 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id 6E86FDA8F5; Wed, 12 Jun 2019 19:51:39 +0200 (CEST) Date: Wed, 12 Jun 2019 19:51:38 +0200 From: David Sterba To: Naohiro Aota Cc: linux-btrfs@vger.kernel.org, David Sterba , Chris Mason , Josef Bacik , Qu Wenruo , Nikolay Borisov , linux-kernel@vger.kernel.org, Hannes Reinecke , linux-fsdevel@vger.kernel.org, Damien Le Moal , Matias =?iso-8859-1?Q?Bj=F8rling?= , Johannes Thumshirn , Bart Van Assche Subject: Re: [PATCH v2 00/19] btrfs zoned block device support Message-ID: <20190612175138.GT3563@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Naohiro Aota , linux-btrfs@vger.kernel.org, David Sterba , Chris Mason , Josef Bacik , Qu Wenruo , Nikolay Borisov , linux-kernel@vger.kernel.org, Hannes Reinecke , linux-fsdevel@vger.kernel.org, Damien Le Moal , Matias =?iso-8859-1?Q?Bj=F8rling?= , Johannes Thumshirn , Bart Van Assche References: <20190607131025.31996-1-naohiro.aota@wdc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190607131025.31996-1-naohiro.aota@wdc.com> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 07, 2019 at 10:10:06PM +0900, Naohiro Aota wrote: > btrfs zoned block device support > > This series adds zoned block device support to btrfs. The overall design sounds ok. I skimmed through the patches and the biggest task I see is how to make the hmzoned adjustments and branches less visible, ie. there are too many if (hmzoned) { do something } standing out. But that's merely a matter of wrappers and maybe an abstraction here and there. How can I test the zoned devices backed by files (or regular disks)? I searched for some concrete example eg. for qemu or dm-zoned, but closest match was a text description in libzbc README that it's possible to implement. All other howtos expect a real zoned device. Merge target is 5.3 or later, we'll see how things will go. I'm expecting that we might need some time to get feedback about the usability as there's no previous work widely used that we can build on top of.