All of lore.kernel.org
 help / color / mirror / Atom feed
From: FUJITA Tomonori <tomof@acm.org>
To: matthew@wil.cx
Cc: linux-scsi@vger.kernel.org, kristen.c.accardi@intel.com,
	fujita.tomonori@lab.ntt.co.jp
Subject: Re: SCSI RAM driver
Date: Tue, 19 Feb 2008 22:14:53 +0900	[thread overview]
Message-ID: <20080219221442L.tomof@acm.org> (raw)
In-Reply-To: <20080218063658.GF21012@parisc-linux.org>

On Sun, 17 Feb 2008 23:36:59 -0700
Matthew Wilcox <matthew@wil.cx> wrote:

> 
> This is the first release of a driver we've been using internally at Intel
> for a few weeks which is as low-latency as possible.  It's designed to
> let us find latency issues elsewhere in the storage stack (eg filesystem,
> block layer, scsi layer)
> 
> There are a few different options, controlled through module parameters.
> The sector size and disc capacity are load-time parameters, but the
> parameters affecting performance are tweakable at runtime.
> 
> Arguably, this driver should be merged into scsi_debug.  I didn't want to
> trip over Doug's toes while developing this driver, and the two drivers
> do have very different objectives.  scsi_debug is obviously a lot more
> fully-featured and implements lots of bits of the spec I simply haven't
> bothered with.  Like MODE SENSE ;-)

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.

If we clean up scsi_debug driver, can scsi_debug work as a nice scsi
ram driver?

  reply	other threads:[~2008-02-19 13:15 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 [this message]
2008-02-19 13:31   ` Matthew Wilcox
2008-02-19 13:46     ` FUJITA Tomonori
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=20080219221442L.tomof@acm.org \
    --to=tomof@acm.org \
    --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.