From: Pankaj Raghav <p.raghav@samsung.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Damien.LeMoal@wdc.com, pankydev8@gmail.com,
linux-f2fs-devel@lists.sourceforge.net, mcgrof@kernel.org,
Adam Manzanares <a.manzanares@samsung.com>,
javier.gonz@samsung.com
Subject: Re: [f2fs-dev] [PATCH v2] libf2fs: don't allow mkfs / fsck on non power-of-2 zoned devices
Date: Wed, 20 Apr 2022 08:48:12 +0200 [thread overview]
Message-ID: <d924fad5-2eed-f850-c191-ee72852393ae@samsung.com> (raw)
In-Reply-To: <Yl9Aw0vLdxM5Fexg@google.com>
On 2022-04-20 01:07, Jaegeuk Kim wrote:>> TL;DR until we change some
calculations in f2fs for zoned device to be
>> generic, we need to bail out during mkfs time for non power of 2 zone
>> size devices.
>
> Ah, I see. Yeah, that in f2fs is actually PO2. Let me merge this patch to
> force it before getting that relax. Thanks,
>
Thanks Jaegeuk. We are working on relaxing the po2 constraint for device
zone sizes for zoned devices in the kernel and we will be sending the
patches soon. I am not sure if we will relax these constraints in f2fs
during the first round of patches but we will eventually get there. When
that happens, we can relax these constraints also in f2fs-tools :).
_______________________________________________
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-20 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220413122941eucas1p1ec05e8e8dfe2baf451fcb549d60fda35@eucas1p1.samsung.com>
2022-04-13 12:29 ` [f2fs-dev] [PATCH v2] libf2fs: don't allow mkfs / fsck on non power-of-2 zoned devices Pankaj Raghav
2022-04-13 17:03 ` Jaegeuk Kim
2022-04-13 17:53 ` Pankaj Raghav
2022-04-13 19:45 ` Jaegeuk Kim
2022-04-19 8:02 ` Pankaj Raghav
2022-04-19 23:07 ` Jaegeuk Kim
2022-04-20 6:48 ` Pankaj Raghav [this message]
2022-04-20 8:30 ` Pankaj Raghav
2022-04-20 10:45 ` Chao Yu
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=d924fad5-2eed-f850-c191-ee72852393ae@samsung.com \
--to=p.raghav@samsung.com \
--cc=Damien.LeMoal@wdc.com \
--cc=a.manzanares@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=javier.gonz@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=mcgrof@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.