linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
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: Wed, 15 Apr 2020 15:15:09 +0800	[thread overview]
Message-ID: <cf8dd5fb-17a8-f6a0-ad54-e70c50a8eff5@huawei.com> (raw)
In-Reply-To: <BN6PR02MB3379ACB0F0777D5D932EF641DEDB0@BN6PR02MB3379.namprd02.prod.outlook.com>

Hi Tim,

On 2020/4/15 10:54, Tim Walker wrote:
>> Hi Chao Yu-
> 
> Yes the zones can have different status, according to the spec. I don't know how many drive manufactures use those zone states - if any. I was only asking to see if I had missed Offline or Read_Only zone support when I examined the f2fs source code. I was interested in the implementation details if support had been included. Thanks!

Unfortunately, that support on f2fs has not been done yet.

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

  reply	other threads:[~2020-04-15  7:15 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
2020-04-15  2:54   ` Tim Walker
2020-04-15  7:15     ` Chao Yu [this message]
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=cf8dd5fb-17a8-f6a0-ad54-e70c50a8eff5@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).