On Mon, Oct 14, 2024 at 09:28:04AM -0700, Daeho Jeong wrote: > On Sun, Oct 13, 2024 at 10:56 PM Christoph Hellwig <h...@infradead.org> wrote: > > > > On Thu, Oct 10, 2024 at 12:26:26PM -0700, Daeho Jeong wrote: > > > From: Daeho Jeong <daehoje...@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 > > > > s/extrent/extent/g > > > > > using node blocks. The file space should be pinned and normally used for > > > read-only usages. > > > > Is there an explanation somewhere what a 'device aliasing file' is? > > Plz, refer to this patch and the description there. > > https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?h=dev-test&id=8cc4e257ec20bee207bb034d5ac406e1ab31eaea
This is about the extent I know, and I'm still utterly confused. _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
