From: Chandan Rajendra <chandan@linux.ibm.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, jaegeuk@kernel.org, yuchao0@huawei.com
Subject: Re: [RFC PATCH 00/10] Consolidate Post read processing code
Date: Fri, 22 Feb 2019 09:59:31 +0530 [thread overview]
Message-ID: <2245787.mQPMR5rap9@localhost.localdomain> (raw)
In-Reply-To: <20190221183827.GA140206@gmail.com>
On Friday, February 22, 2019 12:08:28 AM IST Eric Biggers wrote:
> On Thu, Feb 21, 2019 at 07:02:03PM +0530, Chandan Rajendra wrote:
> > On Wednesday, February 20, 2019 6:11:07 AM IST Eric Biggers wrote:
> > > On Mon, Feb 18, 2019 at 03:34:23PM +0530, Chandan Rajendra wrote:
> > > > Based on the reviews provided for this patchset, I
> > > > will change F2FS to use mpage_readpage[s] and post the next version of
> > > > this patchset to linux-fsdevel mailing list.
> > >
> > > Is that really possible? F2FS has other functionality in its ->readpages(),
> > > such as support for filesystems that use multiple block devices.
> > >
> >
> > Hmm. I didn't know that. Thanks for pointing that out. I will read up that
> > code and if it isn't really possible to get F2FS to use mpage_readpage[s](),
> > then I would limit the patchset to Ext4.
> >
>
> But we can make F2FS use the shared bio_post_read functions even if it can't use
> mpage_readpage[s](), right?
>
Yes, that should be possible. I will include those changes in the next version
of the patchset.
--
chandan
WARNING: multiple messages have this Message-ID (diff)
From: Chandan Rajendra <chandan@linux.ibm.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: tytso@mit.edu, linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, adilger.kernel@dilger.ca,
jaegeuk@kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [RFC PATCH 00/10] Consolidate Post read processing code
Date: Fri, 22 Feb 2019 09:59:31 +0530 [thread overview]
Message-ID: <2245787.mQPMR5rap9@localhost.localdomain> (raw)
In-Reply-To: <20190221183827.GA140206@gmail.com>
On Friday, February 22, 2019 12:08:28 AM IST Eric Biggers wrote:
> On Thu, Feb 21, 2019 at 07:02:03PM +0530, Chandan Rajendra wrote:
> > On Wednesday, February 20, 2019 6:11:07 AM IST Eric Biggers wrote:
> > > On Mon, Feb 18, 2019 at 03:34:23PM +0530, Chandan Rajendra wrote:
> > > > Based on the reviews provided for this patchset, I
> > > > will change F2FS to use mpage_readpage[s] and post the next version of
> > > > this patchset to linux-fsdevel mailing list.
> > >
> > > Is that really possible? F2FS has other functionality in its ->readpages(),
> > > such as support for filesystems that use multiple block devices.
> > >
> >
> > Hmm. I didn't know that. Thanks for pointing that out. I will read up that
> > code and if it isn't really possible to get F2FS to use mpage_readpage[s](),
> > then I would limit the patchset to Ext4.
> >
>
> But we can make F2FS use the shared bio_post_read functions even if it can't use
> mpage_readpage[s](), right?
>
Yes, that should be possible. I will include those changes in the next version
of the patchset.
--
chandan
next prev parent reply other threads:[~2019-02-22 4:29 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 10:04 [RFC PATCH 00/10] Consolidate Post read processing code Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 01/10] ext4: use IS_ENCRYPTED() to check encryption status Chandan Rajendra
2019-02-18 10:04 ` [f2fs-dev] " Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 02/10] f2fs: " Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 03/10] fscrypt: remove filesystem specific build config option Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 04/10] Consolidate "post read processing" into a new file Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-19 23:22 ` Eric Biggers
2019-02-19 23:22 ` [f2fs-dev] " Eric Biggers
2019-02-19 23:22 ` Eric Biggers
2019-02-21 12:51 ` Chandan Rajendra
2019-02-21 12:51 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 05/10] fsverity: Add call back to decide if verity check has to be performed Chandan Rajendra
2019-02-18 10:04 ` [f2fs-dev] " Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-19 23:26 ` [f2fs-dev] " Eric Biggers
2019-02-19 23:26 ` Eric Biggers
2019-02-21 12:54 ` [f2fs-dev] " Chandan Rajendra
2019-02-21 12:54 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 06/10] Introduce REQ_POST_READ_PROC bio flag Chandan Rajendra
2019-02-18 10:04 ` [f2fs-dev] " Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-20 0:21 ` [f2fs-dev] " Eric Biggers
2019-02-20 0:21 ` Eric Biggers
2019-02-21 13:03 ` [f2fs-dev] " Chandan Rajendra
2019-02-21 13:03 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 07/10] fsverity: Add call back to determine readpage limit Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 08/10] fsverity: Add call back to verify file holes Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-20 0:35 ` Eric Biggers
2019-02-20 0:35 ` Eric Biggers
2019-02-21 13:05 ` Chandan Rajendra
2019-02-21 13:05 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 09/10] fs/mpage.c: Integrate post read processing Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-18 10:04 ` [RFC PATCH 10/10] ext4: Wire up ext4_readpage[s] to use mpage_readpage[s] Chandan Rajendra
2019-02-18 10:04 ` Chandan Rajendra
2019-02-18 10:19 ` [RFC PATCH 00/10] Consolidate Post read processing code Chandan Rajendra
2019-02-18 10:19 ` Chandan Rajendra
2019-02-19 21:17 ` Eric Biggers
2019-02-19 21:17 ` [f2fs-dev] " Eric Biggers
2019-02-19 21:17 ` Eric Biggers
2019-02-21 13:29 ` Chandan Rajendra
2019-02-21 13:29 ` Chandan Rajendra
2019-02-20 0:41 ` Eric Biggers
2019-02-20 0:41 ` Eric Biggers
2019-02-21 13:32 ` Chandan Rajendra
2019-02-21 13:32 ` Chandan Rajendra
2019-02-21 18:38 ` Eric Biggers
2019-02-21 18:38 ` Eric Biggers
2019-02-22 4:29 ` Chandan Rajendra [this message]
2019-02-22 4:29 ` Chandan Rajendra
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=2245787.mQPMR5rap9@localhost.localdomain \
--to=chandan@linux.ibm.com \
--cc=adilger.kernel@dilger.ca \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yuchao0@huawei.com \
/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.