From: Alasdair G Kergon <agk@redhat.com>
To: Neil Brown <neilb@suse.de>,
device-mapper development <dm-devel@redhat.com>,
lmb@novell.com
Subject: Re: RFC: multipath IO multiplex
Date: Sat, 6 Nov 2010 11:51:02 +0000 [thread overview]
Message-ID: <20101106115102.GF10171@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20101106053203.7e4ef435@notabene>
On Sat, Nov 06, 2010 at 05:32:03AM -0400, Neil Brown wrote:
> Might it make sense to configure a range of the device where writes always
> went down all paths? That would seem to fit with your problem description
> and might be easiest??
Indeed - a persistent property of the device (even another interface with a
different minor number) not the I/O.
And what is the nature of the data being written, given that I/O to one path
might get delayed and arrive long after it was sent, overwriting data
sent later. Successful stale writes will always be recognised as such
by readers - how?
Alasdair
next prev parent reply other threads:[~2010-11-06 11:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 18:39 RFC: multipath IO multiplex Lars Marowsky-Bree
2010-11-06 9:32 ` Neil Brown
2010-11-06 11:51 ` Alasdair G Kergon [this message]
2010-11-06 16:57 ` Lars Marowsky-Bree
2010-11-07 10:30 ` Christophe Varoqui
2010-11-08 11:50 ` Lars Marowsky-Bree
2010-11-08 12:12 ` Alasdair G Kergon
2010-11-08 12:19 ` Lars Marowsky-Bree
2010-11-08 12:42 ` Hannes Reinecke
2010-11-08 12:56 ` Alasdair G Kergon
2010-11-08 14:18 ` Lars Marowsky-Bree
2010-11-06 17:03 ` Lars Marowsky-Bree
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=20101106115102.GF10171@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=lmb@novell.com \
--cc=neilb@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).