From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Pankaj Raghav <p.raghav@samsung.com>
Cc: javier.gonz@samsung.com, Damien.LeMoal@wdc.com,
mcgrof@kernel.org, pankydev8@gmail.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/3] f2fs-tools: return error for zoned devices with non power-of-2 zone size
Date: Tue, 12 Apr 2022 09:33:39 -0700 [thread overview]
Message-ID: <YlWp468pKUrRLFTH@google.com> (raw)
In-Reply-To: <20220412112745.44108-1-p.raghav@samsung.com>
On 04/12, Pankaj Raghav wrote:
> F2FS only works for zoned devices with power-of-2 zone sizes as the
> f2fs section needs to be a power-of-2.
The section size actually supports multiple 2MBs, not PO2.
>
> At the moment the linux kernel only accepts zoned devices which are
> power-of-2 as block devices but there are zoned devices in the market
> which have non power-of-2 zone sizes.
>
> As a proactive measure, this patchset adds a check to return error
> from mkfs and fsck for zoned devices with non power-of-2 zone sizes.
>
> Luis Chamberlain (3):
> libf2fs_zoned: factor out helper to get chunk sectors
> libf2fs: add support to report zone size
> libf2fs: don't allow mkfs / fsck on zoned NPO2
>
> include/f2fs_fs.h | 1 +
> lib/libf2fs.c | 17 +++++++++++++++--
> lib/libf2fs_zoned.c | 32 ++++++++++++++++++++++----------
> 3 files changed, 38 insertions(+), 12 deletions(-)
>
> --
> 2.25.1
>
>
>
> _______________________________________________
> 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:[~2022-04-12 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220412112746eucas1p14f52961641ef07fdc7274e75887da9ad@eucas1p1.samsung.com>
2022-04-12 11:27 ` [f2fs-dev] [PATCH 0/3] f2fs-tools: return error for zoned devices with non power-of-2 zone size Pankaj Raghav
[not found] ` <CGME20220412112747eucas1p11e2747339407a5c51a93e7b7060ab965@eucas1p1.samsung.com>
2022-04-12 11:27 ` [f2fs-dev] [PATCH 1/3] libf2fs_zoned: factor out helper to get chunk sectors Pankaj Raghav
2022-04-12 12:17 ` Damien Le Moal via Linux-f2fs-devel
[not found] ` <CGME20220412112748eucas1p19a9e013fa04d5a82abd5364604a8ad31@eucas1p1.samsung.com>
2022-04-12 11:27 ` [f2fs-dev] [PATCH 2/3] libf2fs: add support to report zone size Pankaj Raghav
2022-04-12 12:14 ` Damien Le Moal via Linux-f2fs-devel
2022-04-12 16:23 ` Luis Chamberlain
2022-04-13 1:03 ` Damien Le Moal via Linux-f2fs-devel
[not found] ` <CGME20220412112749eucas1p28b82e6b3b563f2e25c78f479c1192451@eucas1p2.samsung.com>
2022-04-12 11:27 ` [f2fs-dev] [PATCH 3/3] libf2fs: don't allow mkfs / fsck on zoned NPO2 Pankaj Raghav
2022-04-12 12:16 ` Damien Le Moal via Linux-f2fs-devel
2022-04-12 15:30 ` Pankaj Raghav
2022-04-12 16:33 ` Jaegeuk Kim [this message]
2022-04-13 11:14 ` [f2fs-dev] [PATCH 0/3] f2fs-tools: return error for zoned devices with non power-of-2 zone size Pankaj Raghav
2022-04-13 16:22 ` Jaegeuk Kim
2022-04-13 17:53 ` Pankaj Raghav
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=YlWp468pKUrRLFTH@google.com \
--to=jaegeuk@kernel.org \
--cc=Damien.LeMoal@wdc.com \
--cc=javier.gonz@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=pankydev8@gmail.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).