lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 14 Apr 2009 09:16:18 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Bart Van Assche <bart.vanassche@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: dm-multipath and write request ordering

Bart Van Assche <bart.vanassche@...il.com> writes:

> - Is it correct that round-robin load balancing can only work
> correctly in such a setup with proper support for write barriers in
> the device mapper ?

No opinion on that one.

> - Did I understand it correctly that the current dm implementation
> only supports barriers when remapping a single underlying device ?

And also only for dm_linear, so probably it doesn't work on dm_mp (haven't
tested) even if it has only a single device.

Barriers over multiple devices are very difficult, at least as long as
the underlying protocol doesn't support shared barriers or the Linux
barrier concept be extended.  The problem is that you cannot express
to the underlying device that some of its requests are dependent on
requests going to other devices.

> - Are there any plans to add barrier support to dm-multipath ?

[note I'm not very familiar with Linux's dm_mp finer details, some 
details here might be wrong]

I doubt it's really doable with RR. It might be possible if you
do the IO primary on one device and only on error fall back to another
device. Then during the fallback you could just synchronize all
IO and solve the barrier problem this way and otherwise do barriers
on the single active device only. But with multiple devices you
would have the problem described above.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ