From: George Dunlap <george.dunlap@eu.citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: Olaf Hering <olaf@aepfle.de>, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Chun Yan Liu <cyliu@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Ian Jackson <ian.jackson@citrix.com>
Subject: Re: [PATCH RFC v1] libxl: Introduce a template for devices with a controller
Date: Wed, 27 May 2015 14:57:33 +0100 [thread overview]
Message-ID: <5565CD4D.4020306@eu.citrix.com> (raw)
In-Reply-To: <556597DA.6090306@suse.com>
On 05/27/2015 11:09 AM, Juergen Gross wrote:
> George,
>
> I'm on vacation this and the next week with only limited email access.
> So please don't expect fast reaction on any further questions during
> this time. :-)
Then quit reading your work e-mail and get back to the important stuff! :-)
>> OK, so I looked it up[1] and the full address seems to be:
>> * adapter number / host
>> * channel number / bus
>> * id number / target
>> * LUN
>>
>> In which case, "controller" would correspond to "adapter / host", right?
>>
>> In the vscsi world, what levels of what can you make? I know you
>> mentioned before that some devices have multiple LUNs, and those need
>> to be grouped together, with the same LUNs as they do on real
>> hardware, to work properly -- is that right?
>
> Not all of the devices have this requirement, but some.
>
>> The USB case actually has something somewhat similar:
>> * USB controller
>> * USB bus
>> * USB device
>> * USB function
>>
>> So far, there's not really a controller/bus distinction: each
>> controller has exactly one bus. When we assign a USB device to a bus,
>> we automatically go through and assign each function fo that device
>> individually.
>>
>> Would it make sense to treat vscsi the same way -- i.e., to make a
>> "bus", and then attach "targets"s to it, and have the LUNs for any
>> given target automatically assigned when the target is assigned?
>
> As long as it is still possible to assign individual LUNs as well.
> If dom0 is controlling e.g. a RAID system you might want to assign
> one LUN of a target to domU A and one LUN of the same target to domU B.
OK, so it sounds like in the vscsi case, it would be useful to assign
either an entire target, or an individual LUN.
In the case of assigning a target, you'll want to assign all the LUNs as
well, such that the virtual LUNs mirror the real LUNs.
In the case of assigning a LUN, I assume you'll still need a virtual
target. Will you be wanting an interface for creating virtual targets,
so that you can assign several real LUNs to the same target? Or will
you just want one virtual target per LUN if you're not assigning an
entire target?
-George
next prev parent reply other threads:[~2015-05-27 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 17:07 [PATCH RFC v1] libxl: Introduce a template for devices with a controller George Dunlap
2015-05-21 17:11 ` George Dunlap
2015-05-21 17:28 ` George Dunlap
2015-05-22 4:21 ` Juergen Gross
2015-05-26 17:56 ` George Dunlap
2015-05-27 10:09 ` Juergen Gross
2015-05-27 13:57 ` George Dunlap [this message]
2015-06-17 11:33 ` Juergen Gross
2015-05-27 14:40 ` Ian Campbell
2015-06-17 11:06 ` Ian Campbell
2015-06-17 11:28 ` Juergen Gross
2015-06-17 13:14 ` Ian Campbell
2015-06-18 5:55 ` Olaf Hering
2015-06-18 5:18 ` Chun Yan Liu
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=5565CD4D.4020306@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=cyliu@suse.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jgross@suse.com \
--cc=olaf@aepfle.de \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.