public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] btrfs: add a test case to verify scrub speed throttle works
Date: Thu, 5 Jan 2023 06:17:28 +0800	[thread overview]
Message-ID: <151e5c83-6de6-9950-d1ce-8a375acea356@oracle.com> (raw)
In-Reply-To: <20230104082123.56800-1-wqu@suse.com>

On 1/4/23 16:21, Qu Wenruo wrote:
> We introduced scrub speed throttle in commit eb3b50536642 ("btrfs: scrub:
> per-device bandwidth control"),  but it is not that well documented
> (e.g. what's the unit of the sysfs interface), nor tested by any test
> case.
> 
> This patch will add a test case for this functionality.
> 
> The test case itself is pretty straightforward:
> 
> - Fill the fs with 2G file as scrub workload
> - Set scrub speed limit to 50MiB/s
> - Scrub and compare the reported rate against above 50MiB/s throttle
> 
> However the test case has an assumption that the underlying disk must be
> faster than our 50MiB/s, which should be pretty common in
> baremetal/exclusive VMs.
> But for cloud environment it's not ensured 100%, thus the test case is
> not included in auto group to avoid false alerts.


Why not scrub the data twice: first to determine the speed, and then to 
check if it can be throttled to ~50%?

-Anand



  reply	other threads:[~2023-01-04 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  8:21 [PATCH] btrfs: add a test case to verify scrub speed throttle works Qu Wenruo
2023-01-04 22:17 ` Anand Jain [this message]
2023-01-04 23:17   ` Qu Wenruo
  -- strict thread matches above, loose matches on Subject: below --
2023-01-05  7:18 Qu Wenruo
2023-01-05 11:04 ` Anand Jain

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=151e5c83-6de6-9950-d1ce-8a375acea356@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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