All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: add a way to limit roll forward recovery time
Date: Tue, 8 Feb 2022 09:43:30 +0800	[thread overview]
Message-ID: <38422afe-fed3-63ab-345f-04ff21c1a1cb@kernel.org> (raw)
In-Reply-To: <YgFsi7cvYOs6oB3e@google.com>

On 2022/2/8 3:01, Jaegeuk Kim wrote:
> This adds a sysfs entry to call checkpoint during fsync() in order to avoid
> long elapsed time to run roll-forward recovery when booting the device.
> Default value doesn't enforce the limitation which is same as before.
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,


_______________________________________________
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: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: add a way to limit roll forward recovery time
Date: Tue, 8 Feb 2022 09:43:30 +0800	[thread overview]
Message-ID: <38422afe-fed3-63ab-345f-04ff21c1a1cb@kernel.org> (raw)
In-Reply-To: <YgFsi7cvYOs6oB3e@google.com>

On 2022/2/8 3:01, Jaegeuk Kim wrote:
> This adds a sysfs entry to call checkpoint during fsync() in order to avoid
> long elapsed time to run roll-forward recovery when booting the device.
> Default value doesn't enforce the limitation which is same as before.
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

  reply	other threads:[~2022-02-08  1:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 21:41 [PATCH] f2fs: add a way to limit roll forward recovery time Jaegeuk Kim
2022-01-27 21:41 ` [f2fs-dev] " Jaegeuk Kim
2022-01-29  8:20 ` Chao Yu
2022-01-29  8:20   ` Chao Yu
2022-02-03  0:33   ` Jaegeuk Kim
2022-02-03  0:33     ` Jaegeuk Kim
2022-02-03  0:34 ` [PATCH v2] " Jaegeuk Kim
2022-02-03  0:34   ` [f2fs-dev] " Jaegeuk Kim
2022-02-03 14:46   ` Chao Yu
2022-02-03 14:46     ` Chao Yu
2022-02-03 17:42     ` Jaegeuk Kim
2022-02-03 17:42       ` Jaegeuk Kim
2022-02-04  0:20       ` Chao Yu
2022-02-04  0:20         ` Chao Yu
2022-02-04  6:16         ` Jaegeuk Kim
2022-02-04  6:16           ` Jaegeuk Kim
2022-02-04 12:03           ` Chao Yu
2022-02-04 12:03             ` Chao Yu
2022-02-07 19:01   ` [f2fs-dev] [PATCH v3] " Jaegeuk Kim
2022-02-07 19:01     ` Jaegeuk Kim
2022-02-08  1:43     ` Chao Yu [this message]
2022-02-08  1:43       ` Chao Yu

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=38422afe-fed3-63ab-345f-04ff21c1a1cb@kernel.org \
    --to=chao@kernel.org \
    --cc=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 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.