All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Kamada <kama@jp.fujitsu.com>
To: Aaron.Dailey@Sun.COM
Cc: kama@jp.fujitsu.com, xen-devel@lists.xensource.com
Subject: Re: Our pvSCSI split driver worked well on NPIV environment
Date: Tue, 18 Sep 2007 19:38:17 +0900	[thread overview]
Message-ID: <20070918192058.5863.KAMA@jp.fujitsu.com> (raw)
In-Reply-To: <46EF602F.4000809@Sun.COM>

Hi Aaron-san,

Thank you for your interests to our pvSCSI split driver. We believe
that there are a lot of situations guest domain would like to issue
SCSI command.

In the near future, we will post the new version of pvSCSI driver
described below.

- Integrate source code of pure SCSI functions and FC transport layer
  functions
- Support reset function
- And fix some bugs


Thanks

kama@jp.fujitsu.com


On Tue, 18 Sep 2007 13:20:47 +0800
Aaron Dailey <Aaron.Dailey@Sun.COM> wrote:
> 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

      reply	other threads:[~2007-09-18 10:38 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
2007-09-18 10:38   ` Jun Kamada [this message]

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=20070918192058.5863.KAMA@jp.fujitsu.com \
    --to=kama@jp.fujitsu.com \
    --cc=Aaron.Dailey@Sun.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.