From: Christoph Hellwig <hch@infradead.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: Daeho Jeong <daehojeong@google.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@infradead.org>,
kernel-team@android.com
Subject: Re: [f2fs-dev] [PATCH v5] f2fs: introduce device aliasing file
Date: Mon, 14 Oct 2024 22:02:18 -0700 [thread overview]
Message-ID: <Zw33WgpF09IHpKLB@infradead.org> (raw)
In-Reply-To: <CACOAw_yvb=jacbXVr76bSbCEcud=D1vw5rJVDO+TjZbMLYzdZQ@mail.gmail.com>
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@infradead.org> wrote:
> >
> > On Thu, Oct 10, 2024 at 12:26:26PM -0700, 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
> >
> > 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
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
Daeho Jeong <daehojeong@google.com>, Chao Yu <chao@kernel.org>
Subject: Re: [PATCH v5] f2fs: introduce device aliasing file
Date: Mon, 14 Oct 2024 22:02:18 -0700 [thread overview]
Message-ID: <Zw33WgpF09IHpKLB@infradead.org> (raw)
In-Reply-To: <CACOAw_yvb=jacbXVr76bSbCEcud=D1vw5rJVDO+TjZbMLYzdZQ@mail.gmail.com>
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@infradead.org> wrote:
> >
> > On Thu, Oct 10, 2024 at 12:26:26PM -0700, 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
> >
> > 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.
next prev parent reply other threads:[~2024-10-15 5:02 UTC|newest]
Thread overview: 16+ 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-10 19:26 ` Daeho Jeong
2024-10-12 2:40 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2024-10-12 2:40 ` Chao Yu
2024-10-14 5:56 ` [f2fs-dev] " Christoph Hellwig
2024-10-14 5:56 ` Christoph Hellwig
2024-10-14 16:28 ` [f2fs-dev] " Daeho Jeong
2024-10-14 16:28 ` Daeho Jeong
2024-10-14 16:42 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2024-10-14 16:42 ` Jaegeuk Kim
2024-10-15 5:05 ` Christoph Hellwig
2024-10-15 5:05 ` Christoph Hellwig
2024-10-15 16:56 ` Jaegeuk Kim
2024-10-15 16:56 ` Jaegeuk Kim via Linux-f2fs-devel
2024-10-15 5:02 ` Christoph Hellwig [this message]
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=Zw33WgpF09IHpKLB@infradead.org \
--to=hch@infradead.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 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.