From: Chao Yu <yuchao0@huawei.com>
To: Tim Walker <timtwalker@outlook.com>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [question] ZBC/ZAC Offline/read-only zone support
Date: Tue, 14 Apr 2020 19:50:54 +0800 [thread overview]
Message-ID: <c81b3ef8-1266-829e-5276-a11e167810c7@huawei.com> (raw)
In-Reply-To: <BN6PR02MB3379134F5821A8D6995E3084DEDA0@BN6PR02MB3379.namprd02.prod.outlook.com>
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
next prev parent reply other threads:[~2020-04-14 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 4:23 [f2fs-dev] [question] ZBC/ZAC Offline/read-only zone support Tim Walker
2020-04-14 11:50 ` Chao Yu [this message]
2020-04-15 2:54 ` Tim Walker
2020-04-15 7:15 ` Chao Yu
2020-04-14 14:09 ` Jaegeuk Kim
2020-04-15 2:49 ` Tim Walker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c81b3ef8-1266-829e-5276-a11e167810c7@huawei.com \
--to=yuchao0@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=timtwalker@outlook.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).