From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [GIT PULL] f2fs for 6.12-rc1
Date: Wed, 25 Sep 2024 03:11:19 +0000 [thread overview]
Message-ID: <ZvN_V-5TfciQ42Pp@google.com> (raw)
In-Reply-To: <CAHk-=wi=dvXyr8b5Z1cYLa-A=-JpYVpJ854UMvftE2gaK==GMg@mail.gmail.com>
On 09/24, Linus Torvalds wrote:
> On Mon, 23 Sept 2024 at 19:42, Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> >
> > In this series, the main changes include 1) converting major IO paths to use
> > folio, and 2) adding various knobs to control GC more flexibly for Zoned
> > devices.
>
> Hmm. I get mostly the same merge result as in linux-next, but I did
> end up with a difference in f2fs_write_begin(). You might want to
> check that out.
>
> That said, the difference is a PAGE_SIZE vs folio_size(folio), and I
> think in the end it doesn't matter because I don't think f2fs does
> large folios yet.
Thank you, it looks fine to me.
>
> But please check it regardless.
>
> Linus
_______________________________________________
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: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] f2fs for 6.12-rc1
Date: Wed, 25 Sep 2024 03:11:19 +0000 [thread overview]
Message-ID: <ZvN_V-5TfciQ42Pp@google.com> (raw)
In-Reply-To: <CAHk-=wi=dvXyr8b5Z1cYLa-A=-JpYVpJ854UMvftE2gaK==GMg@mail.gmail.com>
On 09/24, Linus Torvalds wrote:
> On Mon, 23 Sept 2024 at 19:42, Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> >
> > In this series, the main changes include 1) converting major IO paths to use
> > folio, and 2) adding various knobs to control GC more flexibly for Zoned
> > devices.
>
> Hmm. I get mostly the same merge result as in linux-next, but I did
> end up with a difference in f2fs_write_begin(). You might want to
> check that out.
>
> That said, the difference is a PAGE_SIZE vs folio_size(folio), and I
> think in the end it doesn't matter because I don't think f2fs does
> large folios yet.
Thank you, it looks fine to me.
>
> But please check it regardless.
>
> Linus
next prev parent reply other threads:[~2024-09-25 3:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 2:42 [f2fs-dev] [GIT PULL] f2fs for 6.12-rc1 Jaegeuk Kim via Linux-f2fs-devel
2024-09-24 2:42 ` Jaegeuk Kim
2024-09-24 22:24 ` [f2fs-dev] " Linus Torvalds
2024-09-24 22:24 ` Linus Torvalds
2024-09-25 3:11 ` Jaegeuk Kim via Linux-f2fs-devel [this message]
2024-09-25 3:11 ` Jaegeuk Kim
2024-09-24 22:50 ` [f2fs-dev] " pr-tracker-bot--- via Linux-f2fs-devel
2024-09-24 22:50 ` pr-tracker-bot
2024-09-25 3:41 ` [f2fs-dev] " patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-09-25 3:41 ` patchwork-bot+f2fs
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=ZvN_V-5TfciQ42Pp@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.