dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Lars Marowsky-Bree <lmb@novell.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Christophe Varoqui <christophe.varoqui@gmail.com>
Subject: Re: RFC: multipath IO multiplex
Date: Mon, 8 Nov 2010 12:12:08 +0000	[thread overview]
Message-ID: <20101108121208.GA15253@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20101108115028.GH16210@suse.de>

On Mon, Nov 08, 2010 at 12:50:28PM +0100, Lars Marowsky-Bree wrote:
> I think handling this at the dm-multipath level is cleaner; similarly
> how we handle network bonding (which incidentally has a broadcast mode
> too), instead of requiring every application to go out and open N
> independent channels.
 
Or could it hook into the userspace multipath monitoring code which
already knows the state of the paths?

Well, I'm struggling to see anything clean, simple or generic about
a kernel-side solution here so far.  Seems like a lot of extra kernel
code for just one highly-specialised case: so far I'm unconvinced.

Alasdair

  reply	other threads:[~2010-11-08 12:12 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 [this message]
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=20101108121208.GA15253@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=christophe.varoqui@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=lmb@novell.com \
    /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).