From: "Theodore Ts'o" <tytso@mit.edu>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>, linux-ext4@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Harshad Shirwadkar <harshadshirwadkar@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Ritesh Harjani <riteshh@linux.ibm.com>
Subject: Re: [PATCH 1/2] ext4: Make mb_optimize_scan option work with set/unset mount cmd
Date: Sat, 12 Mar 2022 23:45:40 -0500 [thread overview]
Message-ID: <164714672856.1260831.15800873658441936379.b4-ty@mit.edu> (raw)
In-Reply-To: <c98970fe99f26718586d02e942f293300fb48ef3.1646732698.git.ojaswin@linux.ibm.com>
On Tue, 8 Mar 2022 15:22:00 +0530, Ojaswin Mujoo wrote:
> After moving to the new mount API, mb_optimize_scan mount option
> handling was not working as expected due to the parsed value always
> being overwritten by default. Refactor and fix this to the expected
> behavior described below:
>
> * mb_optimize_scan=1 - On
> * mb_optimize_scan=0 - Off
> * mb_optimize_scan not passed - On if no. of BGs > threshold else off
> * Remounts retain previous value unless we explicitly pass the option
> with a new value
>
> [...]
Applied, thanks!
[1/2] ext4: Make mb_optimize_scan option work with set/unset mount cmd
commit: 27b38686a3bb601db48901dbc4e2fc5d77ffa2c1
[2/2] ext4: Make mb_optimize_scan performance mount option work with extents
commit: 077d0c2c78df6f7260cdd015a991327efa44d8ad
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2022-03-13 4:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 9:52 [PATCH 1/2] ext4: Make mb_optimize_scan option work with set/unset mount cmd Ojaswin Mujoo
2022-03-08 9:52 ` [PATCH 2/2] ext4: Make mb_optimize_scan performance mount option work with extents Ojaswin Mujoo
2022-03-12 5:58 ` [PATCH 1/2] ext4: Make mb_optimize_scan option work with set/unset mount cmd Ritesh Harjani
2022-03-13 4:45 ` Theodore Ts'o [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=164714672856.1260831.15800873658441936379.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=harshadshirwadkar@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=riteshh@linux.ibm.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.