public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org, 0bo0 <0.bugs.only.0@gmail.com>
Subject: Re: does btrfs have RAID I/O throughput (un)limiting sysctls, similar to md?
Date: Sun, 7 Feb 2010 12:48:20 +0100	[thread overview]
Message-ID: <201002071248.20721.Martin@lichtvoll.de> (raw)
In-Reply-To: <c67eed301002060648p436a7347w3c7189e385ed79bc@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 829 bytes --]

Am Samstag 06 Februar 2010 schrieben Sie:
> On Sat, Feb 6, 2010 at 5:10 AM, Daniel J Blueman
> 
> <daniel.blueman@gmail.com> wrote:
> > These proc entries affect just array reconstruction, not general I/O
> > performance/throughput, so affect just an edge-case of applications
> > requiring maximum latency/minimum throughout guarantees.
> 
> although i'd 1st seen the perf hit at the (re)construction stage, i
> didn't recognize that the sysctls were limited to that case.

Limiting rebuild throughput helps to have productively running 
applications getting their share of I/O during RAID rebuilds.
 
> so, iiuc, btrfs has no such issues?

Issues? I would call that a feature, not an issue.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-02-07 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06  0:37 does btrfs have RAID I/O throughput (un)limiting sysctls, similar to md? 0bo0
2010-02-06 13:10 ` Daniel J Blueman
2010-02-06 14:48   ` 0bo0
2010-02-07 11:48     ` Martin Steigerwald [this message]

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=201002071248.20721.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=0.bugs.only.0@gmail.com \
    --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