public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: "Smart, James" <James.Smart@Emulex.com>
Cc: 'James Bottomley' <James.Bottomley@SteelEye.com>,
	"Philip R. Auld" <pauld@egenera.com>,
	'Patrick Mansfield' <patmans@us.ibm.com>,
	Simon Kelley <simon@thekelleys.org.uk>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	dm-devel@sistina.com
Subject: Re: Is there a grand plan for FC failover?
Date: Thu, 29 Jan 2004 10:31:14 -0800	[thread overview]
Message-ID: <20040129183114.GB896@beaverton.ibm.com> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF2802C013BE@xbl.ma.emulex.com>

Smart, James [James.Smart@Emulex.com] wrote:
> 
> 
> > -----Original Message-----
> > From: James Bottomley [mailto:James.Bottomley@SteelEye.com]
> > 
> > On Thu, 2004-01-29 at 09:49, Philip R. Auld wrote:
> > > It needs to be known to the pathing layer if you've got 
> > load balancing. 
> > > It has to know which path has the reservation and only use that one.
> > 
> > Well, yes, but your multiple active path implementation just collapsed
> > back down to single path in the face of reservations, so it would
> > probably be better simply to use failover in the face of reservations
> > and clustering.
> 
> Why do you imply that you're down to a single path ? With multiple port
> devices, and the T10 unclarity on multiport support, simple reservations
> didn't bring you down to the single port access you are describing. Some
> devices may have implemented it this way, but the standard didn't say they
> had to or even that they should.
> 
> And this picture changes significantly with the use of Persistent
> Reservations and the use of keys.
> 

It appears you are mixing port and path. If you have multiple paths to a
port created by multiple adapters connecting to this port through a bus,
fabric, etc. then simple reservations should restrict you to only one
path to this port. Is there a device that implements simple reservations
and allows multiple initiators access?

-andmike
--
Michael Anderson
andmike@us.ibm.com


  reply	other threads:[~2004-01-29 18:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 17:35 Is there a grand plan for FC failover? Smart, James
2004-01-29 18:31 ` Mike Anderson [this message]
2004-01-29 18:31 ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2004-01-29 19:37 Smart, James
2004-01-29 18:41 Smart, James
2004-01-28 21:02 Smart, James
2004-01-28 22:16 ` James Bottomley
2004-01-29 14:49   ` Philip R. Auld
2004-01-29 15:05     ` James Bottomley
2004-01-26 14:18 Simon Kelley
2004-01-26 15:37 ` James Bottomley
2004-01-28 15:02   ` Philip R. Auld
2004-01-28 16:57     ` James Bottomley
2004-01-28 18:00       ` Philip R. Auld
2004-01-28 20:47         ` Patrick Mansfield
2004-01-28 22:14           ` James Bottomley
2004-01-29  0:55             ` Patrick Mansfield
2004-01-28 22:37         ` Mike Christie
2004-01-29 15:24           ` Philip R. Auld
2004-01-29 16:00             ` James Bottomley
2004-01-29 23:25               ` Mike Christie

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=20040129183114.GB896@beaverton.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=James.Smart@Emulex.com \
    --cc=dm-devel@sistina.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.com \
    --cc=pauld@egenera.com \
    --cc=simon@thekelleys.org.uk \
    /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