public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Multi-path IO in 2.5/2.6 ?
Date: Mon, 9 Sep 2002 12:49:44 +0200	[thread overview]
Message-ID: <20020909104944.GH27887@marowsky-bree.de> (raw)

Morning everyone,

I hope people are waking up by now ;-)

So, what is the take on "multi-path IO" (in particular, storage) in 2.5/2.6?

Right now, we have md multipathing in 2.4 (+ an enhancement to that one by
Jens Axboe and myself, which however was ignored on l-k ;-), an enhancement to
LVM1 and various hardware-specific and thus obviously wrong approaches.

I am looking at what to do for 2.5. I have considered porting the small
changes from 2.4 to md 2.5. The LVM1 changes are probably and out gone, as
LVM1 doesn't work still.

I noticed that EVMS duplicates the entire md layer internally (great way to
code, really!), so that might also require changing if I update the md code.

Or can the LVM2 device-mapper be used to do that more cleanly?

I wonder whether anyone has given this some thought already.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
Immortality is an adequate definition of high availability for me.
	--- Gregory F. Pfister


             reply	other threads:[~2002-09-09 10:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09 10:49 Lars Marowsky-Bree [this message]
2002-09-09 12:23 ` [RFC] Multi-path IO in 2.5/2.6 ? Alan Cox
2002-09-10 10:30 ` Heinz J . Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2002-09-09 14:57 James Bottomley
2002-09-09 16:56 ` Patrick Mansfield
2002-09-09 17:34   ` James Bottomley
2002-09-09 18:40     ` Mike Anderson
2002-09-10 13:02       ` Lars Marowsky-Bree
2002-09-10 16:03         ` Patrick Mansfield
2002-09-10 16:27         ` Mike Anderson
2002-09-10  0:08     ` Patrick Mansfield
2002-09-10  7:55       ` Jeremy Higdon
2002-09-10 13:04         ` Lars Marowsky-Bree
2002-09-10 16:20           ` Patrick Mansfield
2002-09-10 13:16       ` Lars Marowsky-Bree
2002-09-10 19:26         ` Patrick Mansfield
2002-09-11 14:20           ` James Bottomley
2002-09-11 19:17             ` Lars Marowsky-Bree
2002-09-11 19:37               ` James Bottomley
2002-09-11 19:52                 ` Lars Marowsky-Bree
2002-09-12  1:15                   ` Bernd Eckenfels
2002-09-11 21:38                 ` Oliver Xymoron
2002-09-11 20:30             ` Doug Ledford
2002-09-11 21:17               ` Mike Anderson
2002-09-10 17:21       ` Patrick Mochel
2002-09-10 18:42         ` Patrick Mansfield
2002-09-10 19:00           ` Patrick Mochel
2002-09-10 19:37             ` Patrick Mansfield
2002-09-11  0:21 ` Neil Brown
2002-09-09 17:58 Ulrich Weigand
2002-09-10 14:06 Cameron, Steve
2002-09-10 14:25 ` Alan Cox
2002-09-10 14:43 Cameron, Steve
2002-09-10 15:05 ` Alan Cox
2002-09-10 16:34 Cameron, Steve
2002-09-10 18:48 ` Alan Cox

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=20020909104944.GH27887@marowsky-bree.de \
    --to=lmb@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox