From: James Smart <James.Smart@Emulex.Com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: Jun Kamada <kama@jp.fujitsu.com>,
Steven Smith <steven.smith@eu.citrix.com>,
xen-devel@lists.xensource.com
Subject: Re: [Patch 0/7] pvSCSI driver
Date: Fri, 14 Mar 2008 15:04:06 -0400 [thread overview]
Message-ID: <47DACC26.2030105@emulex.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D013DBEEB@trantor>
James Harper wrote:
> This reset stuff seems like a lot of extra work for probably not much
> benefit though.
This ends up being the crux of it...
It all depends on how important the use of scsi is to the consumer. In otherwords,
a scsi disk, layered under LVM, filesystems, etc, the nuances of the resets and
inter-relations between luns and targets isn't that meaningful and they will happily
live in a world with these things are emulated.
However, if the scsi disk is talked to directly via things like sg tools, or things
like multipathing software (where failover is disk & target specific), it matters
more.
And if the scsi disk is handed all the way to the database, it matter *much* *much*
more. In fact, this is one reason you find very enterprise databases supported in
virtualized environments.
All this hints at levels of pass-thru. Granted, you can always take one step at a time.
-- james
next prev parent reply other threads:[~2008-03-14 19:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 10:10 [Patch 0/7] pvSCSI driver Jun Kamada
2008-02-18 12:14 ` James Harper
2008-02-19 2:26 ` Jun Kamada
2008-02-19 2:28 ` James Harper
2008-02-20 3:58 ` James Harper
2008-02-20 5:09 ` Jun Kamada
2008-02-21 2:19 ` James Harper
2008-02-21 3:39 ` James Harper
2008-02-21 4:23 ` Jun Kamada
2008-02-21 5:30 ` James Harper
2008-02-25 1:53 ` Jun Kamada
2008-02-27 11:16 ` Steven Smith
2008-02-28 2:51 ` Jun Kamada
2008-02-28 11:13 ` Steven Smith
2008-02-29 4:47 ` Jun Kamada
2008-03-03 11:38 ` Steven Smith
2008-03-04 7:57 ` Jun Kamada
2008-03-04 13:05 ` Steven Smith
2008-03-05 2:34 ` James Harper
2008-03-05 9:53 ` Jun Kamada
2008-03-05 9:56 ` James Harper
2008-03-05 10:00 ` Jun Kamada
2008-03-06 23:48 ` Dan Magenheimer
2008-03-07 1:20 ` Jun Kamada
2008-03-07 2:55 ` Jun Kamada
2008-03-07 4:31 ` James Harper
2008-03-14 19:04 ` James Smart [this message]
2008-03-10 12:00 ` Steven Smith
2008-03-12 6:23 ` Jun Kamada
2008-03-13 14:30 ` Steven Smith
2008-03-17 2:33 ` Jun Kamada
2008-03-17 17:29 ` Steven Smith
2008-03-14 19:16 ` James Smart
2008-03-17 2:59 ` 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=47DACC26.2030105@emulex.com \
--to=james.smart@emulex.com \
--cc=james.harper@bendigoit.com.au \
--cc=kama@jp.fujitsu.com \
--cc=steven.smith@eu.citrix.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.