From: Hannes Reinecke <hare@suse.de>
To: dougg@torque.net
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] ALUA support for scsi_debug
Date: Thu, 19 Oct 2006 09:08:11 +0200 [thread overview]
Message-ID: <4537245B.5090806@suse.de> (raw)
In-Reply-To: <4536602A.5050008@torque.net>
Douglas Gilbert wrote:
> Hannes Reinecke wrote:
>> Hi all,
>>
>> I've hacked up scsi_debug to support REPORT TARGET PORT GROUPS.
>> In combination with vpd_use_hostno=0 it'll now support multipathing
>> nicely.
>> Doug, there is reference to port_a and port_b in the VPD page support.
>> However, port_b appearently is just a fake entry with no (virtual)
>> device backing.
>
> Hannes,
> Yes, I was mimicking a SAS drive with the secondary port
> unconnected.
>
Hmm. We could to that, too. Just set the secondary port to unavailable.
Let's see ...
>> We could eg use the 'channel' value to refer the relative port number,
>> so that host & channel act as a fan-out for multipathing.
>
> I'll have a look, perhaps it could be wired when
> vpd_use_hostno=0 .
>
Yep, that would be possible.
>> James, please apply.
>
> Umm, I would like to find out why that patch oopses
> my machine when I load the scsi_debug module.
>
Not my fault (I hope). Patch works when compiling under 2.6.18 ...
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux Products GmbH S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
-
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:[~2006-10-19 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 14:50 [PATCH] ALUA support for scsi_debug Hannes Reinecke
2006-10-18 17:11 ` Douglas Gilbert
2006-10-19 7:08 ` Hannes Reinecke [this message]
2006-10-18 19:50 ` James Bottomley
2006-10-18 20:18 ` Douglas Gilbert
2006-10-19 13:10 ` Hannes Reinecke
2006-10-19 14:50 ` Douglas Gilbert
2006-10-20 7:58 ` Hannes Reinecke
2006-10-20 20:39 ` Douglas Gilbert
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=4537245B.5090806@suse.de \
--to=hare@suse.de \
--cc=dougg@torque.net \
--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