From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Lukas Herbolt <lherbolt@redhat.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Fwd: All scsi_debug devices in the scsi_debug driver share the same RAM space
Date: Tue, 13 Feb 2018 21:14:45 -0500 [thread overview]
Message-ID: <yq11shoqpuy.fsf@oracle.com> (raw)
In-Reply-To: <CAM4Jq_5yHhEWU6hvUfJVnCpyCk0QPMHhZ7cY3Eum540124ukeQ@mail.gmail.com> (Lukas Herbolt's message of "Mon, 12 Feb 2018 16:04:59 +0100")
Lukas,
> I like the idea to have an option to separate the memory area for
> different LUNs, while keeping the current behavior as default.
As the name implies, scsi_debug is mostly a tool for debugging the SCSI
stack.
If you care about storing data, why not simply use target in loopback
mode?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-02-14 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 19:43 All scsi_debug devices in the scsi_debug driver share the same RAM space Laurence Oberman
2018-02-05 14:32 ` Laurence Oberman
[not found] ` <CAM4Jq_43+JrSTvXsq7kgRLikqHb2iwFMYKTBuQjQ5h2Dn1ka+A@mail.gmail.com>
2018-02-12 15:04 ` Fwd: " Lukas Herbolt
2018-02-14 2:14 ` Martin K. Petersen [this message]
2018-02-14 18:45 ` Laurence Oberman
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=yq11shoqpuy.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=lherbolt@redhat.com \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox