From: "Philip R. Auld" <pauld@egenera.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
agk@redhat.com, dm-devel@redhat.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH RFC] move scsi parts of dm hw handlers to scsi layer
Date: Fri, 21 Jul 2006 08:57:47 -0400 [thread overview]
Message-ID: <20060721125747.GA29177@vienna.egenera.com> (raw)
In-Reply-To: <581472.1153482088210.SLOX.WebMail.wwwrun@imap-dhs.suse.de>
Rumor has it that on Fri, Jul 21, 2006 at 01:41:28PM +0200 Hannes Reinecke said:
> IIRC this is
>
> 'DGC' 'DISK'
> 'DGC' 'RAID 10'
> 'DGC' 'RAID 5'
>
> Hrmph. There is one bit which doesn't quite work out.
> While the hardware handler knows how to handle error codes and how to
> switch
> paths for a specific device, it doesn't know _when_ to switch it.
> I don't think it's a clever idea to switch paths whenever you encounter
> an
> passive path. Seems like you could do a nice ping-pong that way ...
Yes. I agree that having the handlers in SCSI is a better place for
them. However, the architectural decision to have multipath knowledge
at a higher level makes that harder. Some sort of interface into
the scsi layer handlers from the dm/block layer would be more needed.
That way dm or some piece that has the knowledge of the multipath
situation can trigger the failover.
There will still be a need to bubble up information from the decoded
error codes so higher layers can make the correct decision.
Such an interface would need to be in both directions.
Cheers,
Phil
>
> Cheers,
>
> Hannes
>
> -
> 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
--
Philip R. Auld, Ph.D. Egenera, Inc.
Software Architect 165 Forest St.
(508) 858-2628 Marlboro, MA 01752
next prev parent reply other threads:[~2006-07-21 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 11:20 [PATCH RFC] move scsi parts of dm hw handlers to scsi layer Mike Christie
2006-07-21 11:41 ` Hannes Reinecke
2006-07-21 11:49 ` Mike Christie
2006-07-21 11:55 ` [dm-devel] " Mike Christie
2006-07-21 12:10 ` Hannes Reinecke
2006-07-21 12:15 ` [dm-devel] " Mike Christie
2006-07-21 15:16 ` Mike Anderson
2006-07-21 17:00 ` Mike Christie
2006-07-21 20:38 ` Hannes Reinecke
2006-07-21 21:36 ` [dm-devel] " Mike Anderson
2006-07-21 19:35 ` Patrick Mansfield
2006-07-21 12:57 ` Philip R. Auld [this message]
2006-07-21 19:10 ` Edward Goggin
2006-07-21 19:30 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2006-07-21 19:33 egoggin
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=20060721125747.GA29177@vienna.egenera.com \
--to=pauld@egenera.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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