All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: kernel-team@android.com, Daeho Jeong <daehojeong@google.com>,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix checkpoint mount option wrong combination
Date: Mon, 1 Feb 2021 12:11:23 -0800	[thread overview]
Message-ID: <YBhga9OJPcRa7ntk@google.com> (raw)
In-Reply-To: <CACOAw_zW+xnN7pBmTknuJ1=CGiAvVq0sQhe7D6X8sOjgjF_qeg@mail.gmail.com>

On 02/01, Daeho Jeong wrote:
> Actually, I think we need to select one among them, disable, enable
> and merge. I realized my previous understanding about that was wrong.
> In that case of "checkpoint=merge,checkpoint=enable", the last option
> will override the ones before that.
> This is how the other mount options like fsync_mode, whint_mode and etc.
> So, the answer will be "checkpoint=enable". What do you think?

We need to clarify a bit more. :)

mount checkpoint=disable,checkpoint=merge
remount checkpoint=enable,checkpoint=merge

Then, is it going to enable checkpoint with a thread?

> 
> 
> 
> 2021년 2월 1일 (월) 오후 9:40, Chao Yu <chao@kernel.org>님이 작성:
> >
> > On 2021/2/1 8:06, Daeho Jeong wrote:
> > > From: Daeho Jeong <daehojeong@google.com>
> > >
> > > As checkpoint=merge comes in, mount option setting related to
> > > checkpoint had been mixed up. Fixed it.
> > >
> > > Signed-off-by: Daeho Jeong <daehojeong@google.com>
> > > ---
> > >   fs/f2fs/super.c | 11 +++++------
> > >   1 file changed, 5 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> > > index 56696f6cfa86..8231c888c772 100644
> > > --- a/fs/f2fs/super.c
> > > +++ b/fs/f2fs/super.c
> > > @@ -930,20 +930,25 @@ static int parse_options(struct super_block *sb, char *options, bool is_remount)
> > >                               return -EINVAL;
> > >                       F2FS_OPTION(sbi).unusable_cap_perc = arg;
> > >                       set_opt(sbi, DISABLE_CHECKPOINT);
> > > +                     clear_opt(sbi, MERGE_CHECKPOINT);
> > >                       break;
> > >               case Opt_checkpoint_disable_cap:
> > >                       if (args->from && match_int(args, &arg))
> > >                               return -EINVAL;
> > >                       F2FS_OPTION(sbi).unusable_cap = arg;
> > >                       set_opt(sbi, DISABLE_CHECKPOINT);
> > > +                     clear_opt(sbi, MERGE_CHECKPOINT);
> > >                       break;
> > >               case Opt_checkpoint_disable:
> > >                       set_opt(sbi, DISABLE_CHECKPOINT);
> > > +                     clear_opt(sbi, MERGE_CHECKPOINT);
> > >                       break;
> > >               case Opt_checkpoint_enable:
> > >                       clear_opt(sbi, DISABLE_CHECKPOINT);
> > > +                     clear_opt(sbi, MERGE_CHECKPOINT);
> >
> > What if: -o checkpoint=merge,checkpoint=enable
> >
> > Can you please explain the rule of merge/disable/enable combination and their
> > result? e.g.
> > checkpoint=merge,checkpoint=enable
> > checkpoint=enable,checkpoint=merge
> > checkpoint=merge,checkpoint=disable
> > checkpoint=disable,checkpoint=merge
> >
> > If the rule/result is clear, it should be documented.
> >
> > Thanks,
> >
> >
> > >                       break;
> > >               case Opt_checkpoint_merge:
> > > +                     clear_opt(sbi, DISABLE_CHECKPOINT);
> > >                       set_opt(sbi, MERGE_CHECKPOINT);
> > >                       break;
> > >   #ifdef CONFIG_F2FS_FS_COMPRESSION
> > > @@ -1142,12 +1147,6 @@ static int parse_options(struct super_block *sb, char *options, bool is_remount)
> > >               return -EINVAL;
> > >       }
> > >
> > > -     if (test_opt(sbi, DISABLE_CHECKPOINT) &&
> > > -                     test_opt(sbi, MERGE_CHECKPOINT)) {
> > > -             f2fs_err(sbi, "checkpoint=merge cannot be used with checkpoint=disable\n");
> > > -             return -EINVAL;
> > > -     }
> > > -
> > >       /* Not pass down write hints if the number of active logs is lesser
> > >        * than NR_CURSEG_PERSIST_TYPE.
> > >        */
> > >
> 
> 
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel


_______________________________________________
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: Daeho Jeong <daeho43@gmail.com>
Cc: Chao Yu <chao@kernel.org>, Daeho Jeong <daehojeong@google.com>,
	kernel-team@android.com, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix checkpoint mount option wrong combination
Date: Mon, 1 Feb 2021 12:11:23 -0800	[thread overview]
Message-ID: <YBhga9OJPcRa7ntk@google.com> (raw)
In-Reply-To: <CACOAw_zW+xnN7pBmTknuJ1=CGiAvVq0sQhe7D6X8sOjgjF_qeg@mail.gmail.com>

On 02/01, Daeho Jeong wrote:
> Actually, I think we need to select one among them, disable, enable
> and merge. I realized my previous understanding about that was wrong.
> In that case of "checkpoint=merge,checkpoint=enable", the last option
> will override the ones before that.
> This is how the other mount options like fsync_mode, whint_mode and etc.
> So, the answer will be "checkpoint=enable". What do you think?

We need to clarify a bit more. :)

mount checkpoint=disable,checkpoint=merge
remount checkpoint=enable,checkpoint=merge

Then, is it going to enable checkpoint with a thread?

> 
> 
> 
> 2021년 2월 1일 (월) 오후 9:40, Chao Yu <chao@kernel.org>님이 작성:
> >
> > On 2021/2/1 8:06, Daeho Jeong wrote:
> > > From: Daeho Jeong <daehojeong@google.com>
> > >
> > > As checkpoint=merge comes in, mount option setting related to
> > > checkpoint had been mixed up. Fixed it.
> > >
> > > Signed-off-by: Daeho Jeong <daehojeong@google.com>
> > > ---
> > >   fs/f2fs/super.c | 11 +++++------
> > >   1 file changed, 5 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> > > index 56696f6cfa86..8231c888c772 100644
> > > --- a/fs/f2fs/super.c
> > > +++ b/fs/f2fs/super.c
> > > @@ -930,20 +930,25 @@ static int parse_options(struct super_block *sb, char *options, bool is_remount)
> > >                               return -EINVAL;
> > >                       F2FS_OPTION(sbi).unusable_cap_perc = arg;
> > >                       set_opt(sbi, DISABLE_CHECKPOINT);
> > > +                     clear_opt(sbi, MERGE_CHECKPOINT);
> > >                       break;
> > >               case Opt_checkpoint_disable_cap:
> > >                       if (args->from && match_int(args, &arg))
> > >                               return -EINVAL;
> > >                       F2FS_OPTION(sbi).unusable_cap = arg;
> > >                       set_opt(sbi, DISABLE_CHECKPOINT);
> > > +                     clear_opt(sbi, MERGE_CHECKPOINT);
> > >                       break;
> > >               case Opt_checkpoint_disable:
> > >                       set_opt(sbi, DISABLE_CHECKPOINT);
> > > +                     clear_opt(sbi, MERGE_CHECKPOINT);
> > >                       break;
> > >               case Opt_checkpoint_enable:
> > >                       clear_opt(sbi, DISABLE_CHECKPOINT);
> > > +                     clear_opt(sbi, MERGE_CHECKPOINT);
> >
> > What if: -o checkpoint=merge,checkpoint=enable
> >
> > Can you please explain the rule of merge/disable/enable combination and their
> > result? e.g.
> > checkpoint=merge,checkpoint=enable
> > checkpoint=enable,checkpoint=merge
> > checkpoint=merge,checkpoint=disable
> > checkpoint=disable,checkpoint=merge
> >
> > If the rule/result is clear, it should be documented.
> >
> > Thanks,
> >
> >
> > >                       break;
> > >               case Opt_checkpoint_merge:
> > > +                     clear_opt(sbi, DISABLE_CHECKPOINT);
> > >                       set_opt(sbi, MERGE_CHECKPOINT);
> > >                       break;
> > >   #ifdef CONFIG_F2FS_FS_COMPRESSION
> > > @@ -1142,12 +1147,6 @@ static int parse_options(struct super_block *sb, char *options, bool is_remount)
> > >               return -EINVAL;
> > >       }
> > >
> > > -     if (test_opt(sbi, DISABLE_CHECKPOINT) &&
> > > -                     test_opt(sbi, MERGE_CHECKPOINT)) {
> > > -             f2fs_err(sbi, "checkpoint=merge cannot be used with checkpoint=disable\n");
> > > -             return -EINVAL;
> > > -     }
> > > -
> > >       /* Not pass down write hints if the number of active logs is lesser
> > >        * than NR_CURSEG_PERSIST_TYPE.
> > >        */
> > >
> 
> 
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2021-02-01 20:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01  0:06 [f2fs-dev] [PATCH] f2fs: fix checkpoint mount option wrong combination Daeho Jeong
2021-02-01  0:06 ` Daeho Jeong
2021-02-01 12:40 ` [f2fs-dev] " Chao Yu
2021-02-01 12:40   ` Chao Yu
2021-02-01 13:11   ` Daeho Jeong
2021-02-01 13:11     ` Daeho Jeong
2021-02-01 20:11     ` Jaegeuk Kim [this message]
2021-02-01 20:11       ` Jaegeuk Kim
2021-02-01 23:33       ` Daeho Jeong
2021-02-01 23:33         ` Daeho Jeong
2021-02-02  0:41         ` Daeho Jeong
2021-02-02  0:41           ` Daeho Jeong
2021-02-02  1:32           ` Chao Yu
2021-02-02  1:32             ` Chao Yu
2021-02-02  1:28     ` Chao Yu
2021-02-02  1:28       ` 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=YBhga9OJPcRa7ntk@google.com \
    --to=jaegeuk@kernel.org \
    --cc=daeho43@gmail.com \
    --cc=daehojeong@google.com \
    --cc=kernel-team@android.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: 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.