public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolin Liu <liubaolin12138@163.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca, ojaswin@linux.ibm.com,
	ritesh.list@gmail.com, yi.zhang@huawei.com
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	wangguanyu@vivo.com, liubaolin12138@163.com
Subject: [PATCH v3 v3 0/2] add blocks_allocated to mb_stats and clear mb_stats
Date: Wed, 22 Apr 2026 09:50:23 +0800	[thread overview]
Message-ID: <20260422015026.7170-1-liubaolin12138@163.com> (raw)

The series contains two patches:
 - add blocks_allocated to /proc/fs/ext4/<dev>/mb_stats
 - allow writing 0 to /proc/fs/ext4/<dev>/mb_stats to clear the current
   mballoc statistics

Changes since v2: 
 - Add mb_stats documentation to patch 2
 - Add Reviewed-by tags

Baolin Liu (2):
  ext4: add blocks_allocated to mb_stats output
  ext4: allow clearing mballoc stats through mb_stats

 Documentation/admin-guide/ext4.rst |  5 ++++
 Documentation/filesystems/proc.rst |  3 +++
 fs/ext4/ext4.h                     |  1 +
 fs/ext4/mballoc.c                  | 31 +++++++++++++++++++++++
 fs/ext4/sysfs.c                    | 40 ++++++++++++++++++++++++++++--
 5 files changed, 78 insertions(+), 2 deletions(-)

-- 
2.51.0


             reply	other threads:[~2026-04-22  1:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22  1:50 Baolin Liu [this message]
2026-04-22  1:50 ` [PATCH v3 v3 1/2] ext4: add blocks_allocated to mb_stats output Baolin Liu
2026-04-24  2:35   ` Baokun Li
2026-04-22  1:50 ` [PATCH v3 v3 2/2] ext4: allow clearing mballoc stats through mb_stats Baolin Liu
2026-04-23 16:19   ` Theodore Tso
2026-04-24  3:12     ` Baokun Li
2026-04-24  8:09     ` liubaolin
2026-04-24  9:34       ` Baokun Li
2026-04-27  1:29         ` liubaolin
2026-04-24 12:07       ` Theodore Tso
2026-04-27  1:24         ` liubaolin
2026-04-22  9:55 ` [PATCH v3 v3 0/2] add blocks_allocated to mb_stats and clear mb_stats liubaolin

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=20260422015026.7170-1-liubaolin12138@163.com \
    --to=liubaolin12138@163.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.com \
    --cc=tytso@mit.edu \
    --cc=wangguanyu@vivo.com \
    --cc=yi.zhang@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox