public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Hannes Reinecke <hare@suse.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] ALUA support for scsi_debug
Date: Wed, 18 Oct 2006 13:11:06 -0400	[thread overview]
Message-ID: <4536602A.5050008@torque.net> (raw)
In-Reply-To: <20061018145018.GC25084@pentland.suse.de>

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.

> 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 .

> James, please apply.

Umm, I would like to find out why that patch oopses
my machine when I load the scsi_debug module.

lk 2.6.19-rc2 has regressed in a few areas, for example
after an oops, inane messages from atkbd repeat ad
nauseum, making the oops hard to analyse. And my SMC2835W
(prism54 driver) no longer works.

Doug Gilbert


  reply	other threads:[~2006-10-18 17:09 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 [this message]
2006-10-19  7:08   ` Hannes Reinecke
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=4536602A.5050008@torque.net \
    --to=dougg@torque.net \
    --cc=hare@suse.de \
    --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