From: Douglas Gilbert <dgilbert@interlog.com>
To: Olaf Hering <olaf@aepfle.de>, Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: use dedicated storage for scsi_debug LUNs
Date: Thu, 05 Mar 2015 16:22:43 -0500 [thread overview]
Message-ID: <54F8C923.5010202@interlog.com> (raw)
In-Reply-To: <20150305153338.GA16293@aepfle.de>
On 15-03-05 10:33 AM, Olaf Hering wrote:
> I'm using scsi_debug to implement and test tools for xen-scsiback. Today
> I discovered that each LUN uses the very same storage, as described in
> the docs. What would it take to optionally use dedicated storage for
> each LUN?
>
> This is how I load scsi_debug:
> modprobe scsi_debug add_host=4 dev_size_mb=4 max_luns=4 num_parts=4 num_tgts=4 vpd_use_hostno=1
Olaf,
Just having a quick look: the fake_storep, dif_storep and
map_storep heaps would need to be per LU; IOWs placed in
struct sdebug_dev_info. Also atomic_rw would need to be
placed in that structure.
To be backward compatible to what the scsi_debug driver
does now (i.e. shares storage) accessor functions might
be employed to hide whether the global or per LU instance
is being handled.
Handling the inevitable ENOMEM errors might be a bit tricky
especially since extra LUs and hosts can be added dynamically
via sysfs.
So it is possible. The stock answer has typically been that
you should probably be using the target subsystem for that.
Thoughts?
Doug Gilbert
next prev parent reply other threads:[~2015-03-05 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 15:33 use dedicated storage for scsi_debug LUNs Olaf Hering
2015-03-05 21:22 ` Douglas Gilbert [this message]
2015-03-06 9:11 ` Olaf Hering
2015-03-06 12:26 ` Martin K. Petersen
2015-03-06 15:06 ` Olaf Hering
2015-03-06 15:28 ` Martin K. Petersen
2015-03-20 12:07 ` Olaf Hering
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=54F8C923.5010202@interlog.com \
--to=dgilbert@interlog.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=olaf@aepfle.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox