[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zw33WgpF09IHpKLB@infradead.org>
Date: Mon, 14 Oct 2024 22:02:18 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Daeho Jeong <daeho43@...il.com>
Cc: Christoph Hellwig <hch@...radead.org>, linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, kernel-team@...roid.com,
Daeho Jeong <daehojeong@...gle.com>, Chao Yu <chao@...nel.org>
Subject: Re: [PATCH v5] f2fs: introduce device aliasing file
On Mon, Oct 14, 2024 at 09:28:04AM -0700, Daeho Jeong wrote:
> On Sun, Oct 13, 2024 at 10:56 PM Christoph Hellwig <hch@...radead.org> wrote:
> >
> > On Thu, Oct 10, 2024 at 12:26:26PM -0700, Daeho Jeong wrote:
> > > From: Daeho Jeong <daehojeong@...gle.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.
Powered by blists - more mailing lists