From: Ming Zhang <blackmagic02881@gmail.com>
To: Ming Zhao <mingzhao99th@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>,
bert hubert <bert.hubert@netherlabs.nl>,
ming@acis.ufl.edu, Linux Kernel <linux-kernel@vger.kernel.org>,
ericvh@gmail.com
Subject: Re: [dm-devel] Re: [RFC][PATCH] dm-cache: block level disk cache target for device mapper
Date: Sat, 02 Dec 2006 13:35:36 -0500 [thread overview]
Message-ID: <1165084536.5456.9.camel@localhost.localdomain> (raw)
In-Reply-To: <b1e142760612021028t522ba3ffs485bc70d93a85774@mail.gmail.com>
On Sat, 2006-12-02 at 13:28 -0500, Ming Zhao wrote:
> On 12/1/06, Ming Zhang <blackmagic02881@gmail.com> wrote:
> > like to see this idea but any similarity with
> > http://www.ele.uri.edu/Research/hpcl/STICS/stics.pdf?
> >
> > STICS is patent pending so not sure if kernel can be free to merge this
> > dm-cache.
>
> I like the idea of STICS, an efficient bridge between SCSI and IP. But
> I think its only similarity with dm-cache is the use of nonvolatile
> caching.
>
> Dm-cache is a generic block-level disk cache that supports a variety
> of SAN technologies and is not tied to any particular one.
>
great. as long as you are aware of this and can find the difference,
then fine.
>
> Best regards,
> Ming Zhao
next prev parent reply other threads:[~2006-12-02 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 18:26 Eric Van Hensbergen
2006-11-27 18:47 ` bert hubert
2006-11-27 19:55 ` Eric Van Hensbergen
2006-12-02 1:21 ` [dm-devel] " Ming Zhang
2006-12-02 18:28 ` Ming Zhao
2006-12-02 18:35 ` Ming Zhang [this message]
2006-11-30 11:32 ` [dm-devel] " Jens Wilke
2006-11-30 16:24 ` Eric Van Hensbergen
2006-11-30 20:07 ` Jens Wilke
2006-12-01 7:16 ` Ming Zhao
2006-12-01 10:30 ` Jens Wilke
2006-11-30 14:48 ` Christoph Hellwig
2006-12-11 18:54 ` Eric Van Hensbergen
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=1165084536.5456.9.camel@localhost.localdomain \
--to=blackmagic02881@gmail.com \
--cc=bert.hubert@netherlabs.nl \
--cc=dm-devel@redhat.com \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming@acis.ufl.edu \
--cc=mingzhao99th@gmail.com \
/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
Powered by JetHome