From: Christoph Hellwig <hch@infradead.org>
To: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH v4 2/6] ext4: add ability to return parsed options from parse_options
Date: Mon, 15 Mar 2021 19:06:18 +0000 [thread overview]
Message-ID: <20210315190618.GA150808@infradead.org> (raw)
In-Reply-To: <20210315173716.360726-3-harshadshirwadkar@gmail.com>
On Mon, Mar 15, 2021 at 10:37:12AM -0700, Harshad Shirwadkar wrote:
> Before this patch, the function parse_options() was returning
> journal_devnum and journal_ioprio variables to the caller. This patch
> generalizes that interface to allow parse_options to return any parsed
> options to return back to the caller. In this patch series, it gets
> used to capture the value of "mb_optimize_scan=%u" mount option.
Instead of adding more code to the legacy option parsing code can
someone convert ext4 to the new mount API first?
next prev parent reply other threads:[~2021-03-15 19:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 17:37 Block allocator improvements Harshad Shirwadkar
2021-03-15 17:37 ` [PATCH v4 1/6] ext4: drop s_mb_bal_lock and convert protected fields to atomic Harshad Shirwadkar
2021-03-15 17:37 ` [PATCH v4 2/6] ext4: add ability to return parsed options from parse_options Harshad Shirwadkar
2021-03-15 19:06 ` Christoph Hellwig [this message]
2021-03-17 11:11 ` Благодаренко Артём
2021-03-15 17:37 ` [PATCH v4 3/6] ext4: add mballoc stats proc file Harshad Shirwadkar
2021-03-15 17:37 ` [PATCH v4 4/6] ext4: add MB_NUM_ORDERS macro Harshad Shirwadkar
2021-03-15 17:37 ` [PATCH v4 5/6] ext4: improve cr 0 / cr 1 group scanning Harshad Shirwadkar
2021-03-15 20:56 ` Andreas Dilger
2021-03-16 7:55 ` Dan Carpenter
2021-03-22 15:33 ` Благодаренко Артём
2021-03-22 17:25 ` harshad shirwadkar
2021-03-15 17:37 ` [PATCH v4 6/6] ext4: add proc files to monitor new structures Harshad Shirwadkar
2021-03-15 19:52 ` Andreas Dilger
2021-03-15 19:52 ` Block allocator improvements Andreas Dilger
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=20210315190618.GA150808@infradead.org \
--to=hch@infradead.org \
--cc=harshadshirwadkar@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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