From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH v5] f2fs: introduce device aliasing file
Date: Sat, 12 Oct 2024 10:40:42 +0800 [thread overview]
Message-ID: <54325522-b7fa-4629-bc90-ca5e5127ae85@kernel.org> (raw)
In-Reply-To: <20241010192626.1597226-1-daeho43@gmail.com>
On 2024/10/11 3:26, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> F2FS should understand how the device aliasing file works and support
> deleting the file after use. A device aliasing file can be created by
> mkfs.f2fs tool and it can map the whole device with an extrent, not
> using node blocks. The file space should be pinned and normally used for
> read-only usages.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> Signed-off-by: Chao Yu <chao@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
> ---
> v5: added a ioctl to know whether a file is for device aliasing
IMO, maybe we need to add a common wrapper to export all trivial flags of
f2fs, which can improve scalability, it benefits the case whenever we want
to export new flags.
Thanks,
_______________________________________________
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:[~2024-10-12 2:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 19:26 [f2fs-dev] [PATCH v5] f2fs: introduce device aliasing file Daeho Jeong
2024-10-12 2:40 ` Chao Yu via Linux-f2fs-devel [this message]
2024-10-14 5:56 ` Christoph Hellwig
2024-10-14 16:28 ` Daeho Jeong
2024-10-14 16:42 ` Jaegeuk Kim via Linux-f2fs-devel
2024-10-15 5:05 ` Christoph Hellwig
2024-10-15 16:56 ` Jaegeuk Kim via Linux-f2fs-devel
2024-10-15 5:02 ` Christoph Hellwig
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=54325522-b7fa-4629-bc90-ca5e5127ae85@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
/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