From: Aaron Dailey <Aaron.Dailey@Sun.COM>
To: Jun Kamada <kama@jp.fujitsu.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Our pvSCSI split driver worked well on NPIV environment
Date: Tue, 18 Sep 2007 13:20:47 +0800 [thread overview]
Message-ID: <46EF602F.4000809@Sun.COM> (raw)
In-Reply-To: <20070831081947.1936.KAMA@jp.fujitsu.com>
Kamada-san and all,
We're also working on an NPIV driver for Solaris xVM (see
http://www.news.com/8301-13580_3-9778296-39.html for what xVM means).
I've looked at the pvSCSI split driver, and I think it's valuable for
both NPIV FibreChannel and standard SCSI environments. Especially with
NPIV though it will become valuable because we can dedicate one virtual
HBA to a DOMU, and use those devices as SCSI devices.
I see it as especially valuable for tape, but also for non standard SCSI
devices. Also some users may want to use it for disk instead of using
the block driver. For example, in Solaris, we can control write cache on
disk drives differently depending on SCSI status, information which
would be unavailable via block interface.
Regards,
Aaron
Jun Kamada wrote:
> Hi all,
>
> We have successfully made our pvSCSI split driver works on NPIV
> environment. This means that each guest domain can exclusively use own
> "logical" HBA even if the host machine have only one "physical" HBA.
> We believe that our pvSCSI split driver is useful on NPIV environment
> and is needed for enterprise domain.
>
> Following are evaluation environment.
>
> [Hardware]
> Host machine： Fujitsu PRIMERGY RX300 S3 (IA32 machine)
> FC-Switch: Fujitsu Eternus SN200 Model430
> Storage: Fujitsu Eternus 4000
>
> [Software]
> Xen 3.1
> Linux Kernel： 2.6.18
>
> Please refer following URL about the pvSCSI split driver.
>
> http://lists.xensource.com/archives/html/xen-devel/2007-07/msg00450.html
> http://lists.xensource.com/archives/html/xen-devel/2007-07/msg00451.html
> http://lists.xensource.com/archives/html/xen-devel/2007-07/msg00452.html
> http://lists.xensource.com/archives/html/xen-devel/2007-07/msg00453.html
> http://lists.xensource.com/archives/html/xen-devel/2007-07/msg00561.html
>
> http://lists.xensource.com/archives/html/xen-devel/2007-08/msg00002.html
>
> Best regards,
>
> -----
> Jun Kamada
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2007-09-18 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 23:44 Our pvSCSI split driver worked well on NPIV environment Jun Kamada
2007-09-18 5:20 ` Aaron Dailey [this message]
2007-09-18 10:38 ` 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=46EF602F.4000809@Sun.COM \
--to=aaron.dailey@sun.com \
--cc=kama@jp.fujitsu.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.