From: "Josef Möllers" <josef.moellers@fujitsu-siemens.com>
To: "jansen, frank" <jansen_frank@emc.com>
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@steeleye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Summary of the Multi-Path BOF at OLS and future directions
Date: Fri, 08 Aug 2003 15:27:18 +0200 [thread overview]
Message-ID: <3F33A536.F0C3F1C5@fujitsu-siemens.com> (raw)
In-Reply-To: 64655AAA92E6ED46B9AC9421260D96A5025BD654@srmanning.lss.emc.com
"jansen, frank" wrote:
>
> > Josef Möllers wrote
> >
> > With MultiPath it _is_ necessary to TRESPASS a CLARiiON box if each SP
> > is conected to a seperate path.
> >
> To access the non-active path, this is correct. What I was trying to say
> is that the MultiPath layer should be somewhat intelligent about this and
> be aware that there may be another active path. It is much quicker to go
> down an active path than trespass a LUN and then do the I/O. The other
> part is the risk of excessive trespassing, where a LUN just gets bounced
> back and forth between SPs for each I/O; this is an absolute worst case
> that would bring performance to a standstill.
Obviously.
What we did was to do a TRESPASS only if a command failed with certain
sense data:
ILLEGAL REQUEST, LUN NOT READY, CAUSE NOT REPORTABLE.
Have a nice weekend
--
Josef Möllers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-08-08 13:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 12:28 Summary of the Multi-Path BOF at OLS and future directions jansen, frank
2003-08-08 13:27 ` Josef Möllers [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-08 12:13 jansen, frank
2003-08-08 12:15 ` Christoph Hellwig
2003-08-08 12:21 ` Josef Möllers
2003-08-05 3:54 James Bottomley
2003-08-05 16:48 ` Alan Cox
2003-08-05 17:06 ` James Bottomley
2003-08-07 11:00 ` Alan Cox
2003-08-06 0:14 ` Patrick Mansfield
2003-08-06 20:26 ` Steven Dake
2003-08-07 7:38 ` Lars Marowsky-Bree
2003-08-07 16:20 ` Christoph Hellwig
2003-08-07 23:54 ` Tim Pepper
2003-08-08 6:45 ` Josef Möllers
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=3F33A536.F0C3F1C5@fujitsu-siemens.com \
--to=josef.moellers@fujitsu-siemens.com \
--cc=James.Bottomley@steeleye.com \
--cc=hch@infradead.org \
--cc=jansen_frank@emc.com \
--cc=linux-scsi@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