On Fri, Apr 08, 2016 at 10:36:07AM +0200, Zdenek Kabelac wrote:
> However now the multipathd *kills* this assumption - since the current udev
> rules implementation for multipath devices targets only for the initial scan
> and all subsequent RESUMES are supposed to be ignored as it's believed the
On Fri, Apr 08 2016 at 3:03pm -0400,
Mike Snitzer wrote:
> On Fri, Apr 08 2016 at 2:58pm -0400,
> Mike Snitzer wrote:
>
> > The DM multipath service-time path-selector has historically tracked the
> > amount of outstanding IO per path and used that to
On Fri, Apr 08 2016 at 2:58pm -0400,
Mike Snitzer wrote:
> The DM multipath service-time path-selector has historically tracked the
> amount of outstanding IO per path and used that to approximate the
> service-time of each path. In practice this has shown itself to work
>
The DM multipath service-time path-selector has historically tracked the
amount of outstanding IO per path and used that to approximate the
service-time of each path. In practice this has shown itself to work
fairly well but we can do better by measuring the actual service-time
during IO
Ladies and Gentlemen,
To show off some numbers from our testing:
All tests are performed against the cache of the Array, not the disks as we
wanted to test the Linux stack not the Disk Array.
All single queue tests have been performed with the deadline I/O Scheduler.
Comments welcome, have fun
Dne 8.4.2016 v 01:20 Benjamin Marzinski napsal(a):
lvm needs PV devices to not be suspended while the udev rules are
running, for them to be correctly identified as PVs. However, multipathd
will often be in a situation where it will create a multipath device
upon seeing a path, and then