public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: liubaolin <liubaolin12138@163.com>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
	tytso@mit.edu, adilger.kernel@dilger.ca
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	wangguanyu@vivo.com, Baolin Liu <liubaolin@kylinos.cn>
Subject: Re: [PATCH v1] ext4: add mb_stats_clear for mballoc statistics
Date: Thu, 16 Apr 2026 15:16:08 +0800	[thread overview]
Message-ID: <0e075abc-11f2-40f3-9dd3-566cd54a2bae@163.com> (raw)
In-Reply-To: <mrz3u1a4.ritesh.list@gmail.com>

> Dear Ritesh,
> Thank you for your review. I will revise the patch according to Andreas's comments and submit a second version. 
> When the second version is submitted, you are welcome to review it. 
> Once the patch is finalized, the maintainer will add the Reviewed-by tag.
> 
> Regards,
> Baolin



在 2026/4/16 9:44, Ritesh Harjani (IBM) 写道:
> Baolin Liu <liubaolin12138@163.com> writes:
> 
>> From: Baolin Liu <liubaolin@kylinos.cn>
>>
>> Add a write-only mb_stats_clear sysfs knob to reset ext4 mballoc
>> runtime statistics.This makes it easier to inspect allocator
>> activity for a specific workload instead of using counters
>> accumulated since mount.
>>
>> Signed-off-by: Baolin Liu <liubaolin@kylinos.cn>
> 
> Make sense to me. The changes looks good and works fine at my end.
> So please feel free to add:
> 
> Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>


  reply	other threads:[~2026-04-16  7:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 10:02 [PATCH v1] ext4: add mb_stats_clear for mballoc statistics Baolin Liu
2026-04-14 10:07 ` liubaolin
2026-04-15 19:26 ` Ojaswin Mujoo
2026-04-16  7:07   ` liubaolin
2026-04-16  1:14 ` Andreas Dilger
2026-04-16  7:11   ` liubaolin
2026-04-16  1:44 ` Ritesh Harjani
2026-04-16  7:16   ` liubaolin [this message]
2026-04-16  8:53 ` Zhang Yi

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=0e075abc-11f2-40f3-9dd3-566cd54a2bae@163.com \
    --to=liubaolin12138@163.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liubaolin@kylinos.cn \
    --cc=ritesh.list@gmail.com \
    --cc=tytso@mit.edu \
    --cc=wangguanyu@vivo.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