Hi,
I am just figuring out the performance issues - thanks guys for this bug
description!
It looks like the problem remains unsolved:
$iostat -cd
Linux 4.4.0-63-generic (ruprecht) 21.2.2017 _x86_64_(8 CPU)
avg-cpu: %user %nice %system %iowait %steal %idle
It would be great if @lifeless could try attempting to contact dm-devel
again. This is a very important patch that would provide large benefit
across a variety of systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
it would be great if @lifeless could try attempting dm-devel again. This
is a very important patch that will provide large benefit across a
variety of systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
three years and this issue haven't been solved. (at least not as a proven
release, rather unproved patches)
what we need to do to make it happen?
i'm using dual boot in my computer - windows 8 ubuntu 12.10. using intel rst
(rapid storage technology) and unfortunately i see that reading passed
I've forwarded it upstream http://www.redhat.com/archives/dm-
devel/2012-June/msg00013.html but had no reply so far. Any advice on how
to get upstream to look at it would be wonderful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@robert,
If you can get that patch accepted upstream we can get it through a
stable patch. However, it isn't SRU material and we're not going to
carry it on our own.
** Tags added: kt-worked
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/361733
Title:
dmraid(fakeRAID) raid1 driver doesn't loadbalance reads
To manage notifications about this bug go to:
I personally cannot run this command because I do not have an Ubuntu
system in this configuration at this time. Also, this bug is easily
confirmed by simple inspection of the Linux kernel source. It behaves
exactly in accordance with how the code is written, although how it's
written is
Here is an implementation of load balancing; this chooses the closest
drive for a read UI, which results in doing sequential IO from one drive
(and this works a lot better than round-robin per-IO: dm mapping happens
before IO request merging - doing round-robin results in no request
merging and
Nice patch! It should be pushed upstream.
Also, is this design now superior to the mdraid implementation? Should
similar changes be made over there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks. Just followed my nose ;).
So this implementation handles two sequential IO operations happening
at once as-well or better than the md implementation - the md
implementation tracks sequential IO at the array level and at the
result-of-an-IO level, but due to tagged IOs the latter can be
A while back, I changed my doctoral specialization to computer
architecture. But prior to that, I was studying AI, and as I think
about this, this problem screams for a reinforcement learning approach.
For N drives, there are 2N+1 actions, those being read to each drive,
write to each drive, and
I've retitled this bug - while its true that there being two
implementations is an issue, the actual problem folk are running into is
the load balancing issue; beyond that the way in which it is solved is
orthogonal (merge drivers, implement the same balancing algorithm, ...)
** Summary changed:
13 matches
Mail list logo
