From: FUJITA Tomonori <tomof@acm.org>
To: matthew@wil.cx
Cc: tomof@acm.org, linux-scsi@vger.kernel.org,
kristen.c.accardi@intel.com, fujita.tomonori@lab.ntt.co.jp,
dougg@torque.netfujita.tomonori@lab.ntt.co.jp
Subject: Re: SCSI RAM driver
Date: Tue, 19 Feb 2008 22:46:57 +0900 [thread overview]
Message-ID: <20080219224653G.tomof@acm.org> (raw)
In-Reply-To: <20080219133120.GA23001@parisc-linux.org>
On Tue, 19 Feb 2008 06:31:20 -0700
Matthew Wilcox <matthew@wil.cx> wrote:
> On Tue, Feb 19, 2008 at 10:14:53PM +0900, FUJITA Tomonori wrote:
> > I see that two drivers have very different objectives but if we add
> > use_thread option to scsi_debug (we can do easily), it seems that
> > scsi_debug can provide all the features that scsi_ram does.
>
> It's not just use_thread. It's also discard_read/discard_write.
scsi_debug has a similar option, fake_rw, which discards both read and
write data.
> And scsi_ram has a different data storage model from scsi_debug --
> scsi_debug simulates an arbitrarily sized disc by wrapping around some
> small (virtually) contiguous allocation of pages; scsi_ram actually
> allocates the amount of ram that it's told to. This can be solved with
> another module parameter, of course.
IIRC, if virtual_gb option is set to zero, scsi_debug allocates the
amount of ram that it's told to.
> I'm in no way opposed to merging the two; it's a question of whether
> Doug will mind me doing some surgery on his driver.
next prev parent reply other threads:[~2008-02-19 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 6:36 SCSI RAM driver Matthew Wilcox
2008-02-19 13:14 ` FUJITA Tomonori
2008-02-19 13:31 ` Matthew Wilcox
2008-02-19 13:46 ` FUJITA Tomonori [this message]
2008-03-02 10:59 ` 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=20080219224653G.tomof@acm.org \
--to=tomof@acm.org \
--cc=dougg@torque.netfujita.tomonori \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=kristen.c.accardi@intel.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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.