From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Jim Salter <jim@jrs-s.net>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs scrub ioprio
Date: Mon, 25 Nov 2013 08:05:34 -0500 [thread overview]
Message-ID: <52934B1E.9080205@gmail.com> (raw)
In-Reply-To: <529348D4.8080105@jrs-s.net>
On 2013-11-25 07:55, Jim Salter wrote:
> Can you elaborate on this please? I'm not directly familiar with
> cgroups, I'd greatly appreciate a quick-and-dirty example of using BIO
> cgroup to limit I/O bandwidth.
>
> Limiting bandwidth definitely would ameliorate the problem for me; I
> already use pv's bw-limiting feature to make btrfs send | btrfs receive
> tolerable.
>
> On 11/25/2013 07:25 AM, Austin S Hemmelgarn wrote:
>> 2. allow the user to set a reasonable I/O bandwidth limit on the scrub
>> processes (you could already do this with the BIO cgroup, but it would
>> be nice to not need that to be compiled into the kernel to have this
>> happen)
>
I'm not very clear on the specifics, (the only cgroup I personally use
with any regularity is freezer), but I would suggest looking at
Documentation/cgroups/blkio-controller.txt in the kernel source tree
(cgroups are one of the better subsystems WRT documentation). I'm
pretty certain that most distributions have the required kernel options
compiled in by default, and automatically mount the needed filesystems.
next prev parent reply other threads:[~2013-11-25 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 3:45 btrfs scrub ioprio Jim Salter
2013-11-25 12:25 ` Austin S Hemmelgarn
2013-11-25 12:55 ` Jim Salter
2013-11-25 13:05 ` Austin S Hemmelgarn [this message]
2013-11-26 0:50 ` Holger Hoffstaette
2014-01-19 13:49 ` Kai Krakow
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=52934B1E.9080205@gmail.com \
--to=ahferroin7@gmail.com \
--cc=jim@jrs-s.net \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).