From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Andi Kleen <ak@suse.de>
Subject: Re: dm-multipath and write request ordering
Date: Thu, 16 Apr 2009 19:38:13 +0400 [thread overview]
Message-ID: <49E750E5.7010106@vlnb.net> (raw)
In-Reply-To: <e2e108260904130422k2ac92e64jb5aff1cc2adc8da0@mail.gmail.com>
Bart Van Assche, on 04/13/2009 03:22 PM wrote:
> Hello,
>
> Several people are using the dm-multipath software as follows:
> * Linux server A is using dm-multipath to access data stored on
> servers B and C via two iSCSI sessions -- one session between servers
> A and B and one session between servers A and C.
> * On servers B and C iSCSI target software exports a block device that
> is replicated between servers B and C.
>
> Round-robin load balancing will only work correctly in such a setup if
> the replication software knows the order in which write requests have
> been queued on the dm-multipath device. Since iSCSI uses the TCP/IP
> protocol, write requests generated by server A can arrive out-of-order
> on servers B and C. My questions are as follows:
> - 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 ?
Not necessary. If replication between B and C done synchronously,
barriers are not needed. Barriers are necessary only for async commands,
when the next command sent before the previous one completed.
Vlad
prev parent reply other threads:[~2009-04-16 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 11:22 dm-multipath and write request ordering Bart Van Assche
2009-04-14 7:16 ` Andi Kleen
2009-04-14 8:17 ` Bart Van Assche
2009-04-16 15:38 ` Vladislav Bolkhovitin [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=49E750E5.7010106@vlnb.net \
--to=vst@vlnb.net \
--cc=ak@suse.de \
--cc=bart.vanassche@gmail.com \
--cc=linux-kernel@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 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.