From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: decompress data without workqueue
Date: Wed, 18 May 2022 15:35:30 -0700 [thread overview]
Message-ID: <YoV0sm9W+2A644PZ@google.com> (raw)
In-Reply-To: <20220518175547.3284875-1-jaegeuk@kernel.org>
Please hold any test, since this patch has a bug.
On 05/18, Jaegeuk Kim wrote:
> Let's decompress data under the same context to avoid workqueue delay.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/data.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 54a7a8ad994d..37aa7ac5d463 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -285,10 +285,12 @@ static void f2fs_read_end_io(struct bio *bio)
> return;
> }
>
> - if (ctx && (ctx->enabled_steps & (STEP_DECRYPT | STEP_DECOMPRESS))) {
> + if (ctx && (ctx->enabled_steps & STEP_DECRYPT)) {
> INIT_WORK(&ctx->work, f2fs_post_read_work);
> queue_work(ctx->sbi->post_read_wq, &ctx->work);
> } else {
> + if (ctx && (ctx->enabled_steps & STEP_DECOMPRESS))
> + f2fs_handle_step_decompress(ctx);
> f2fs_verify_and_finish_bio(bio);
> }
> }
> --
> 2.36.1.124.g0e6072fb45-goog
prev parent reply other threads:[~2022-05-18 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 17:55 [PATCH] f2fs: decompress data without workqueue Jaegeuk Kim
2022-05-18 22:35 ` Jaegeuk Kim [this message]
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=YoV0sm9W+2A644PZ@google.com \
--to=jaegeuk@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).