From: Jaegeuk Kim <jaegeuk@kernel.org> To: Chao Yu <chao@kernel.org> Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, Eric Biggers <ebiggers@google.com> Subject: Re: [f2fs-dev] [PATCH 5/6] f2fs: implement iomap operations Date: Wed, 5 Jan 2022 10:25:53 -0800 [thread overview] Message-ID: <YdXiscxIceQWw2ZG@google.com> (raw) In-Reply-To: <f8c0d9f8-6a1f-e7b7-4dd3-fcd31272a0df@kernel.org> On 01/05, Chao Yu wrote: > On 2022/1/5 5:24, Jaegeuk Kim wrote: > > From: Eric Biggers <ebiggers@google.com> > > > > Implement 'struct iomap_ops' for f2fs, in preparation for making f2fs > > use iomap for direct I/O. > > > > Note that this may be used for other things besides direct I/O in the > > future; however, for now I've only tested it for direct I/O. > > > > Signed-off-by: Eric Biggers <ebiggers@google.com> > > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org> > > Reviewed-by: Chao Yu <chao@kernel.org> Ditto. Thanks, > > Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org> To: Chao Yu <chao@kernel.org> Cc: Eric Biggers <ebiggers@google.com>, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Subject: Re: [f2fs-dev] [PATCH 5/6] f2fs: implement iomap operations Date: Wed, 5 Jan 2022 10:25:53 -0800 [thread overview] Message-ID: <YdXiscxIceQWw2ZG@google.com> (raw) In-Reply-To: <f8c0d9f8-6a1f-e7b7-4dd3-fcd31272a0df@kernel.org> On 01/05, Chao Yu wrote: > On 2022/1/5 5:24, Jaegeuk Kim wrote: > > From: Eric Biggers <ebiggers@google.com> > > > > Implement 'struct iomap_ops' for f2fs, in preparation for making f2fs > > use iomap for direct I/O. > > > > Note that this may be used for other things besides direct I/O in the > > future; however, for now I've only tested it for direct I/O. > > > > Signed-off-by: Eric Biggers <ebiggers@google.com> > > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org> > > Reviewed-by: Chao Yu <chao@kernel.org> Ditto. Thanks, > > 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:[~2022-01-05 18:26 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-04 21:24 [PATCH 1/6] f2fs: rework write preallocations Jaegeuk Kim 2022-01-04 21:24 ` [f2fs-dev] " Jaegeuk Kim 2022-01-04 21:24 ` [PATCH 2/6] f2fs: reduce indentation in f2fs_file_write_iter() Jaegeuk Kim 2022-01-04 21:24 ` [f2fs-dev] " Jaegeuk Kim 2022-01-04 21:24 ` [PATCH 3/6] f2fs: do not expose unwritten blocks to user by DIO Jaegeuk Kim 2022-01-04 21:24 ` [f2fs-dev] " Jaegeuk Kim 2022-01-05 13:19 ` Chao Yu 2022-01-05 13:19 ` Chao Yu 2022-01-05 18:25 ` Jaegeuk Kim 2022-01-05 18:25 ` Jaegeuk Kim 2022-01-07 23:13 ` Eric Biggers 2022-01-07 23:13 ` [f2fs-dev] " Eric Biggers 2022-01-08 1:52 ` Jaegeuk Kim 2022-01-08 1:52 ` [f2fs-dev] " Jaegeuk Kim 2022-01-08 2:21 ` Eric Biggers 2022-01-08 2:21 ` [f2fs-dev] " Eric Biggers 2022-01-08 3:35 ` Jaegeuk Kim 2022-01-08 3:35 ` [f2fs-dev] " Jaegeuk Kim 2022-01-08 4:21 ` Eric Biggers 2022-01-08 4:21 ` Eric Biggers 2022-01-04 21:24 ` [PATCH 4/6] f2fs: fix the f2fs_file_write_iter tracepoint Jaegeuk Kim 2022-01-04 21:24 ` [f2fs-dev] " Jaegeuk Kim 2022-01-04 21:24 ` [f2fs-dev] [PATCH 5/6] f2fs: implement iomap operations Jaegeuk Kim 2022-01-04 21:24 ` Jaegeuk Kim 2022-01-05 13:20 ` [f2fs-dev] " Chao Yu 2022-01-05 13:20 ` Chao Yu 2022-01-05 18:25 ` Jaegeuk Kim [this message] 2022-01-05 18:25 ` Jaegeuk Kim 2022-01-04 21:24 ` [PATCH 6/6] f2fs: use iomap for direct I/O Jaegeuk Kim 2022-01-04 21:24 ` [f2fs-dev] " Jaegeuk Kim -- strict thread matches above, loose matches on Subject: below -- 2021-11-16 21:45 [PATCH 1/6] f2fs: rework write preallocations Jaegeuk Kim 2021-11-16 21:45 ` [f2fs-dev] [PATCH 5/6] f2fs: implement iomap operations Jaegeuk Kim 2021-12-02 3:10 ` Chao Yu 2021-12-02 3:10 ` Chao Yu 2021-12-02 4:15 ` Eric Biggers 2021-12-02 4:15 ` Eric Biggers 2021-12-02 14:04 ` Chao Yu 2021-12-02 14:04 ` Chao Yu 2021-12-02 18:25 ` Eric Biggers 2021-12-02 18:25 ` Eric Biggers 2021-12-02 18:57 ` Jaegeuk Kim 2021-12-02 18:57 ` Jaegeuk Kim 2021-12-02 19:00 ` Jaegeuk Kim 2021-12-02 19:00 ` Jaegeuk Kim 2021-12-02 20:57 ` Eric Biggers 2021-12-02 20:57 ` Eric Biggers 2021-12-02 21:19 ` Jaegeuk Kim 2021-12-02 21:19 ` Jaegeuk Kim 2021-12-02 21:28 ` Jaegeuk Kim 2021-12-02 21:28 ` Jaegeuk Kim 2021-12-03 6:51 ` Chao Yu 2021-12-03 6:51 ` Chao Yu 2021-12-30 6:43 ` Chao Yu 2021-12-30 6:43 ` Chao Yu 2022-01-04 21:15 ` Jaegeuk Kim 2022-01-04 21:15 ` Jaegeuk Kim
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=YdXiscxIceQWw2ZG@google.com \ --to=jaegeuk@kernel.org \ --cc=chao@kernel.org \ --cc=ebiggers@google.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: linkBe 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.