From: Kent Overstreet <koverstreet@google.com>
To: Michel Lespinasse <walken@google.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Amit Kale <akale@stec-inc.com>,
linux-bcache <linux-bcache@vger.kernel.org>,
device-mapper development <dm-devel@redhat.com>,
Kent Overstreet <kent.overstreet@gmail.com>,
Mike Snitzer <snitzer@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, Jason Warr <jason@warr.net>,
thornber@redhat.com
Subject: Re: [RFC] [DONOTAPPLY] [PATCH] enhanceio: STEC EnhanceIO SSD caching software for Linux kernel
Date: Fri, 1 Feb 2013 17:23:00 -0800 [thread overview]
Message-ID: <CAH+dOxLDVsrmuh2b+RVxwOd0+JOQ+LsbuRYB5zqTE7DnoA+XTA@mail.gmail.com> (raw)
In-Reply-To: <CANN689ExTyhZBiQ-pg3jw+sA4X459qcy3kpt82n3obJ=9AVceQ@mail.gmail.com>
On Fri, Feb 1, 2013 at 4:57 PM, Michel Lespinasse <walken@google.com> wrote:
> On Fri, Feb 1, 2013 at 4:44 PM, Darrick J. Wong <darrick.wong@oracle.com> wrote:
>> This is a patch to migrate STEC's enhanceio driver out of their github
>> repository and into the staging tree. From their README:
>>
>> "EnhanceIO driver is based on EnhanceIO SSD caching software product developed
>> by STEC Inc. EnhanceIO was derived from Facebook's open source Flashcache
>> project. EnhanceIO uses SSDs as cache devices for traditional rotating hard
>> disk drives (referred to as source volumes throughout this document).
>> EnhanceIO can work with any block device, be it an entire physical disk, an
>> individual disk partition, a RAIDed DAS device, a SAN volume, a device mapper
>> volume or a software RAID (md) device."
>
> What's your take on the benefits of this vs bcache ?
I've been trying to review it it for cache coherency and consistency
wrt. power failures, but the complete lack of high level documentation
is making that difficult.
I saw some benchmarks the other day where on writes EIO was faster
than the raw device, which was... suspicious.
WARNING: multiple messages have this Message-ID (diff)
From: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
To: Michel Lespinasse <walken-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: "Darrick J. Wong"
<darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
Amit Kale <akale-FZ1t8LVTR2ZWk0Htik3J/w@public.gmane.org>,
linux-bcache
<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
device-mapper development
<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Kent Overstreet
<kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Jason Warr <jason-/cow75dQlsI@public.gmane.org>,
thornber-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [RFC] [DONOTAPPLY] [PATCH] enhanceio: STEC EnhanceIO SSD caching software for Linux kernel
Date: Fri, 1 Feb 2013 17:23:00 -0800 [thread overview]
Message-ID: <CAH+dOxLDVsrmuh2b+RVxwOd0+JOQ+LsbuRYB5zqTE7DnoA+XTA@mail.gmail.com> (raw)
In-Reply-To: <CANN689ExTyhZBiQ-pg3jw+sA4X459qcy3kpt82n3obJ=9AVceQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Feb 1, 2013 at 4:57 PM, Michel Lespinasse <walken-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> wrote:
> On Fri, Feb 1, 2013 at 4:44 PM, Darrick J. Wong <darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> wrote:
>> This is a patch to migrate STEC's enhanceio driver out of their github
>> repository and into the staging tree. From their README:
>>
>> "EnhanceIO driver is based on EnhanceIO SSD caching software product developed
>> by STEC Inc. EnhanceIO was derived from Facebook's open source Flashcache
>> project. EnhanceIO uses SSDs as cache devices for traditional rotating hard
>> disk drives (referred to as source volumes throughout this document).
>> EnhanceIO can work with any block device, be it an entire physical disk, an
>> individual disk partition, a RAIDed DAS device, a SAN volume, a device mapper
>> volume or a software RAID (md) device."
>
> What's your take on the benefits of this vs bcache ?
I've been trying to review it it for cache coherency and consistency
wrt. power failures, but the complete lack of high level documentation
is making that difficult.
I saw some benchmarks the other day where on writes EIO was faster
than the raw device, which was... suspicious.
next prev parent reply other threads:[~2013-02-02 1:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 0:44 [RFC] [DONOTAPPLY] [PATCH] enhanceio: STEC EnhanceIO SSD caching software for Linux kernel Darrick J. Wong
2013-02-02 0:57 ` Michel Lespinasse
2013-02-02 1:23 ` Kent Overstreet [this message]
2013-02-02 1:23 ` Kent Overstreet
2013-02-02 1:25 ` Kent Overstreet
2013-02-02 1:25 ` Kent Overstreet
2013-02-02 1:39 ` Amit Kale
2013-02-02 1:39 ` Amit Kale
2013-02-02 1:49 ` Darrick J. Wong
2013-02-06 22:57 ` Amit Kale
2013-02-07 0:00 ` Kent Overstreet
2013-02-07 0:00 ` Kent Overstreet
2013-02-07 1:54 ` Amit Kale
2013-02-07 1:54 ` Amit Kale
2013-02-09 9:09 ` Joseph Glanville
2013-02-11 7:04 ` Amit Kale
2013-02-11 7:04 ` Amit Kale
2013-02-04 14:40 ` thornber
2013-02-04 14:40 ` thornber-H+wXaHxf7aLQT0dZR+AlfA
2013-02-04 16:30 ` Amit Kale
2013-02-04 16:30 ` Amit Kale
2013-02-04 20:53 ` Darrick J. Wong
2013-02-04 20:53 ` Darrick J. Wong
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=CAH+dOxLDVsrmuh2b+RVxwOd0+JOQ+LsbuRYB5zqTE7DnoA+XTA@mail.gmail.com \
--to=koverstreet@google.com \
--cc=akale@stec-inc.com \
--cc=darrick.wong@oracle.com \
--cc=dm-devel@redhat.com \
--cc=jason@warr.net \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=thornber@redhat.com \
--cc=walken@google.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 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.