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=-2.1 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 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 970FBC2BA19 for ; Tue, 14 Apr 2020 11:51:19 +0000 (UTC) Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 63684206D5; Tue, 14 Apr 2020 11:51:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sourceforge.net header.i=@sourceforge.net header.b="gMXHWLhm"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sf.net header.i=@sf.net header.b="KpETmYnq" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 63684206D5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linux-f2fs-devel-bounces@lists.sourceforge.net Received: from [127.0.0.1] (helo=sfs-ml-4.v29.lw.sourceforge.com) by sfs-ml-4.v29.lw.sourceforge.com with esmtp (Exim 4.90_1) (envelope-from ) id 1jOK60-0003ea-Eh; Tue, 14 Apr 2020 11:51:16 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-4.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jOK5z-0003eT-9V for linux-f2fs-devel@lists.sourceforge.net; Tue, 14 Apr 2020 11:51:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=XLxLAs/egI8vtYoB3v0LuXjZ1u+jzC+FQI98loMoHF4=; b=gMXHWLhmARtxJDjMi3yxkioSeV BVpHxXzv0dBjQnxdmJDDDUJitgc2GtAilj24rE75oj3LDKL+7tbEmnk013o0bKmKe9Ty3OSrUBK10 m0CIwgx28etxKslnCkp6BYrS55AiR8gYqUYy3sx3FGkTroKdo1XrNMUR1RW2NgxGzeUA=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=XLxLAs/egI8vtYoB3v0LuXjZ1u+jzC+FQI98loMoHF4=; b=KpETmYnqKe/k4uKlBcjKBkx6+E TfdDI+LMZYHWWp8WnzPpvpRqP8f/kLWcAporPYSGWpTsQG2x3OB5KhypvfTQmWX4gbUb/4BGyTiJJ nYa0M0wHEZm/eMqCqpYY/OtbFeiC/KPH76tZt3MgvxiaGPmFgPlRhX1B7Tb2J9CrDkzI=; Received: from szxga06-in.huawei.com ([45.249.212.32] helo=huawei.com) by sfi-mx-1.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.2) id 1jOK5w-00FkNe-OE for linux-f2fs-devel@lists.sourceforge.net; Tue, 14 Apr 2020 11:51:15 +0000 Received: from DGGEMS402-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id 423F69CEE555CC6FCEA4 for ; Tue, 14 Apr 2020 19:50:59 +0800 (CST) Received: from [10.134.22.195] (10.134.22.195) by smtp.huawei.com (10.3.19.202) with Microsoft SMTP Server (TLS) id 14.3.487.0; Tue, 14 Apr 2020 19:50:54 +0800 To: Tim Walker , "linux-f2fs-devel@lists.sourceforge.net" References: From: Chao Yu Message-ID: Date: Tue, 14 Apr 2020 19:50:54 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Originating-IP: [10.134.22.195] X-CFilter-Loop: Reflected X-Headers-End: 1jOK5w-00FkNe-OE Subject: Re: [f2fs-dev] [question] ZBC/ZAC Offline/read-only zone support X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net Hi, On 2020/4/14 12:23, Tim Walker wrote: > Hello- > > I am trying to determine how f2fs handles an offline (or read-only) zone when it is backed by a host-managed SMR HDD. I haven't been able to find any specific code path that places an offline zone into a separate list, or a path that checks the zone condition. Do we support a zone going read-only or offline? Thanks for the info. So you mean different zones in SMR device can have different status? some of them can be tagged as readonly? if my understanding is correct, f2fs needs to handle such readonly zone correctly, e.g. write/discard IO should be avoided being issued to those zones, right? Thanks, > > Best regards, > Tim Walker > > _______________________________________________ > Linux-f2fs-devel mailing list > Linux-f2fs-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel > . > _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel