All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Kamada <kama@jp.fujitsu.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: kama@jp.fujitsu.com,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0/6] pvSCSI (SCSI pass through) driver
Date: Mon, 05 Nov 2007 11:05:58 +0900	[thread overview]
Message-ID: <20071105105812.031C.KAMA@jp.fujitsu.com> (raw)
In-Reply-To: <1193919281.6422.11.camel@sisko.scot.redhat.com>

Hi Stephen-san,

On Thu, 01 Nov 2007 12:14:41 +0000
"Stephen C. Tweedie" <sct@redhat.com> wrote:
> On Tue, 2007-10-30 at 19:39 +0900, Jun Kamada wrote:
> 
> Is this using the same syntax for HBA reservation that we used to have,
> ie. simply enumerated using the scsi host number on the dom0?

Yes.

> If so, that is rather fragile.  The scsi host number can change from
> kernel to kernel depending on HBA driver probe order and PCI bus
> enumeration order.  It changes when hardware is rearranged.  And how do
> we deal with migrate, when we'll need to select a completely different
> HBA on a different host?
> 
> Selecting the HBA by scsi host number is good enough for a demonstration
> that the code works, but I don't think it's going to be robust enough
> for production deployment.  

We also recognize that more sophisticated interface is needed. WWPN can
be used for FC-SCSI, however pure SCSI does not have any unique ID.
Do you have any idea?

> Also, has there been any progress towards exposing individual LUNs to
> the guest rather than a whole HBA?
> 
> Cheers, 
>  Stephen
> 

Jun Kamada
Linux Technology Development Div.
Server Systems Unit
Fujitsu Ltd.
kama@jp.fujitsu.com

  parent reply	other threads:[~2007-11-05  2:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  5:15 [PATCH 0/5] pvSCSI (SCSI pass through) driver Jun Kamada
2007-10-19  8:38 ` Keir Fraser
2007-10-19 10:20   ` Ian Pratt
2007-10-22  2:39     ` Jun Kamada
2007-10-22  0:07 ` James Harper
2007-10-23  7:41   ` Jun Kamada
2007-10-22  8:58 ` Keir Fraser
2007-10-23  7:09   ` Jun Kamada
2007-10-23  8:50     ` Keir Fraser
2007-10-23 11:35       ` Jun Kamada
2007-10-23 12:39         ` Keir Fraser
2007-10-24  6:22           ` Jun Kamada
2007-10-24  7:42             ` Keir Fraser
2007-10-25  1:59               ` Jun Kamada
2007-10-30 10:39                 ` [PATCH 0/6] " Jun Kamada
2007-10-30 10:56                   ` Keir Fraser
2007-10-31  8:37                     ` Jun Kamada
2007-10-31  9:10                       ` Keir Fraser
2007-10-31 10:56                         ` Jun Kamada
2007-10-31 11:15                           ` Keir Fraser
2007-11-01 12:14                   ` Stephen C. Tweedie
2007-11-02  0:23                     ` James Harper
2007-11-05  3:30                       ` Jun Kamada
2007-11-05  2:05                     ` Jun Kamada [this message]
2007-11-08 21:33                       ` Stephen C. Tweedie
2007-11-12  8:27                         ` Jun Kamada
2007-11-05  3:34                     ` Aaron Dailey
2007-10-30 10:39                 ` [PATCH 1/6] " Jun Kamada
2007-10-30 10:39                 ` [PATCH 2/6] " Jun Kamada
2007-10-30 10:39                 ` [PATCH 3/6] " Jun Kamada
2007-10-30 10:39                 ` [PATCH 4/6] " Jun Kamada
2007-10-30 10:39                 ` [PATCH 5/6] " Jun Kamada
2007-10-30 10:39                 ` [PATCH 6/6] " Jun Kamada

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=20071105105812.031C.KAMA@jp.fujitsu.com \
    --to=kama@jp.fujitsu.com \
    --cc=sct@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.