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;
From:   Naohiro Aota <Naohiro.Aota@wdc.com>
To:     "dsterba@suse.cz" <dsterba@suse.cz>
CC:     "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
        David Sterba <dsterba@suse.com>, Chris Mason <clm@fb.com>,
        Josef Bacik <josef@toxicpanda.com>, Qu Wenruo <wqu@suse.com>,
        Nikolay Borisov <nborisov@suse.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Hannes Reinecke <hare@suse.com>,
        "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
        Damien Le Moal <Damien.LeMoal@wdc.com>,
        =?iso-8859-1?Q?Matias_Bj=F8rling?= <mb@lightnvm.io>,
        Johannes Thumshirn <jthumshirn@suse.de>,
        Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH v2 00/19] btrfs zoned block device support
Thread-Topic: [PATCH v2 00/19] btrfs zoned block device support
Thread-Index: AQHVHTKAMt+QxADp/024sRBo1BQ8yw==
Date:   Thu, 13 Jun 2019 04:59:23 +0000
Message-ID: <SN6PR04MB5231E2F482B8D794950058FF8CEF0@SN6PR04MB5231.namprd04.prod.outlook.com>
References: <20190607131025.31996-1-naohiro.aota@wdc.com>
 <20190612175138.GT3563@twin.jikos.cz>
Accept-Language: en-US
Content-Language: en-US
wdcipoutbound: EOP-TRUE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 88ee645f-50c3-4ca4-d0d8-08d6efbbe721
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jun 2019 04:59:23.3460
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b61c8803-16f3-4c35-9b17-6f65f441df86
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Naohiro.Aota1@wdc.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR04MB5469
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 2019/06/13 2:50, David Sterba wrote:=0A=
> On Fri, Jun 07, 2019 at 10:10:06PM +0900, Naohiro Aota wrote:=0A=
>> btrfs zoned block device support=0A=
>>=0A=
>> This series adds zoned block device support to btrfs.=0A=
> =0A=
> The overall design sounds ok.=0A=
> =0A=
> I skimmed through the patches and the biggest task I see is how to make=
=0A=
> the hmzoned adjustments and branches less visible, ie. there are too=0A=
> many if (hmzoned) { do something } standing out. But that's merely a=0A=
> matter of wrappers and maybe an abstraction here and there.=0A=
=0A=
Sure. I'll add some more abstractions in the next version.=0A=
=0A=
> How can I test the zoned devices backed by files (or regular disks)? I=0A=
> searched for some concrete example eg. for qemu or dm-zoned, but closest=
=0A=
> match was a text description in libzbc README that it's possible to=0A=
> implement. All other howtos expect a real zoned device.=0A=
=0A=
You can use tcmu-runer [1] to create an emulated zoned device backed by =0A=
a regular file. Here is a setup how-to:=0A=
http://zonedstorage.io/projects/tcmu-runner/#compilation-and-installation=
=0A=
=0A=
[1] https://github.com/open-iscsi/tcmu-runner=0A=
=0A=
> Merge target is 5.3 or later, we'll see how things will go. I'm=0A=
> expecting that we might need some time to get feedback about the=0A=
> usability as there's no previous work widely used that we can build on=0A=
> top of.=0A=
> =0A=