From: Jun Kamada <kama@jp.fujitsu.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: kama@jp.fujitsu.com, Ian.Pratt@cl.cam.ac.uk,
xen-devel@lists.xensource.com
Subject: Re: [RFC] [0/4] PV driver for FC transport layer
Date: Fri, 06 Jul 2007 15:44:16 +0900 [thread overview]
Message-ID: <20070706152653.BDBA.KAMA@jp.fujitsu.com> (raw)
In-Reply-To: <20070706092215B.fujita.tomonori@lab.ntt.co.jp>
Hi, Fujita-san,
On Fri, 06 Jul 2007 09:22:15 +0900
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> > We are planning to run a storage management software, which controls
> > bindings storages on FC network to hosts, on group of guest domains.
> > The software expect that each guest domain has each HBA, and control the
> > HBA directly. (Ex. resetting SCSI bus and getting WWN, ...)
>
> How do you support storage management software that uses non-scsi?
Current our scope is only SCSI on FC.
What do you mean as the "non-scsi" ?
-----
Jun Kamada
Linux Technology Development Div.
Server Systems Unit
Fujitsu Ltd.
kama@jp.fujitsu.com
next prev parent reply other threads:[~2007-07-06 6:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 11:04 [RFC] [0/4] PV driver for FC transport layer Jun Kamada
2007-06-29 11:06 ` [RFC] [1/4] PV driver for FC transport layer (config files for pv-scsi) Jun Kamada
2007-06-29 11:06 ` [RFC] [2/4] PV driver for FC transport layer (pv-scsi backend driver) Jun Kamada
2007-06-29 11:07 ` [RFC] [3/4] PV driver for FC transport layer (pv-scsi frontend driver) Jun Kamada
2007-06-29 11:08 ` [RFC] [4/4] PV driver for FC transport layer (FC transport layer driver) Jun Kamada
2007-07-03 0:07 ` [RFC] [0/4] PV driver for FC transport layer Ian Pratt
2007-07-04 11:03 ` Jun Kamada
2007-07-06 0:22 ` FUJITA Tomonori
2007-07-06 6:44 ` Jun Kamada [this message]
2007-07-06 7:26 ` FUJITA Tomonori
2007-07-06 8:54 ` Jun Kamada
2007-07-06 0:22 ` FUJITA Tomonori
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=20070706152653.BDBA.KAMA@jp.fujitsu.com \
--to=kama@jp.fujitsu.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=fujita.tomonori@lab.ntt.co.jp \
--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.