All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timofey Titovets <nefelim4ag@gmail.com>
To: Zdenek Kaspar <zkaspar82@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Better data balancing over multiple devices for raid1/10 (read)
Date: Tue, 1 Jan 2019 20:26:57 +0300	[thread overview]
Message-ID: <CAGqmi741ozn5vq+Fwk9bDiuFBMCf-EOaYKgKYKr5ZwTTsULWnw@mail.gmail.com> (raw)
In-Reply-To: <acf42b0d-4c38-8010-f50b-92aed2444884@gmail.com>

вт, 18 дек. 2018 г. в 19:43, Zdenek Kaspar <zkaspar82@gmail.com>:
>
> Hello, regarding Wiki/Idea pool:
> Better data balancing over multiple devices for raid1/10 (read)
>
> By looking at [1] (which I currently use) and [2, 3, 4]
> is there agreement to solve this?
>
> [1] https://patchwork.kernel.org/patch/10681671/
> [2] https://patchwork.kernel.org/patch/10403299/
> [3] https://patchwork.kernel.org/patch/10403303/
> [4] https://patchwork.kernel.org/patch/10403301/
>
> TIA, Z.

I think none of that,
because moreover that patches try solve different problems from my
point of view.

[1] Just try to squeeze more iops from same hardware by simple playing around
with some rules of queueing theory.

[2..4] Try add some duct tape to control over raid1 mirror read for
automatization and testing purposes
(i'm really prefer use sysfs knobs for that type of things).

If you try to read some mailing list conversations about above
patches, you will see
what currently we have no consensus about that solutions.
With no consensus with some majority of devs no progress will be made.

In theory that will be cool to do something similar to mdraid1, where
guys implement internal scheduling policy,
to help balance request over more complex and smart underline disk io
schedulers. That solution
can get consensus from devs POV.
But currently no one work on that, so I guess what in the near future
no agreement will be made.

-- 
Have a nice day,
Timofey.

      reply	other threads:[~2019-01-01 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 16:38 Better data balancing over multiple devices for raid1/10 (read) Zdenek Kaspar
2019-01-01 17:26 ` Timofey Titovets [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=CAGqmi741ozn5vq+Fwk9bDiuFBMCf-EOaYKgKYKr5ZwTTsULWnw@mail.gmail.com \
    --to=nefelim4ag@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zkaspar82@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.