dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@novell.com>
To: Christophe Varoqui <christophe.varoqui@gmail.com>,
	device-mapper development <dm-devel@redhat.com>,
	Neil Brown <neilb@suse.de>
Subject: Re: RFC: multipath IO multiplex
Date: Mon, 8 Nov 2010 15:18:38 +0100	[thread overview]
Message-ID: <20101108141838.GN16210@suse.de> (raw)
In-Reply-To: <20101108125638.GB15253@agk-dp.fab.redhat.com>

On 2010-11-08T12:56:38, Alasdair G Kergon <agk@redhat.com> wrote:

> > I wonder how other latency-sensitive IO handles multipath? Maybe they
> > just haven't noticed yet they'd like a facility like this? ;-)
> As usual, it's the lack of a cancellation interface for incomplete I/O
> that seems to make the kernel-side option troublesome: we still have
> to wait for timeouts.

That would apply just as well to user-space though, no?

Like I said, the goal would be to report the first successful IO
completion, or the last failure - any other failures or results simply
get discarded at the kernel level. (Or wherever.)

> Do we prevent more than one I/O being sent in this mode, given that
> any other alternative would have races?

I don't follow. What races?

Of course the application needs to know this, and can't just treat it
like a regular block device.


Regards,
    Lars

-- 
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

  reply	other threads:[~2010-11-08 14:18 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
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 [this message]
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=20101108141838.GN16210@suse.de \
    --to=lmb@novell.com \
    --cc=christophe.varoqui@gmail.com \
    --cc=dm-devel@redhat.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).