[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <C4B5704C6FEB5244B2A1BCC8CF83B86B0A624D66FE@MYMBX.MY.STEC-INC.AD>
Date: Thu, 7 Feb 2013 06:57:40 +0800
From: Amit Kale <akale@...c-inc.com>
To: Michel Lespinasse <walken@...gle.com>,
"Darrick J. Wong" <darrick.wong@...cle.com>
CC: linux-bcache <linux-bcache@...r.kernel.org>,
device-mapper development <dm-devel@...hat.com>,
Kent Overstreet <kent.overstreet@...il.com>,
Mike Snitzer <snitzer@...hat.com>,
LKML <linux-kernel@...r.kernel.org>, Jason Warr <jason@...r.net>,
"thornber@...hat.com" <thornber@...hat.com>
Subject: RE: [RFC] [DONOTAPPLY] [PATCH] enhanceio: STEC EnhanceIO SSD
caching software for Linux kernel
> -----Original Message-----
> From: Michel Lespinasse [mailto:walken@...gle.com]
> Sent: Friday, February 01, 2013 4:58 PM
> To: Darrick J. Wong
> Cc: Amit Kale; linux-bcache; device-mapper development; Kent
> Overstreet; Mike Snitzer; LKML; Jason Warr; thornber@...hat.com
> Subject: Re: [RFC] [DONOTAPPLY] [PATCH] enhanceio: STEC EnhanceIO SSD
> caching software for Linux kernel
>
> On Fri, Feb 1, 2013 at 4:44 PM, Darrick J. Wong
> <darrick.wong@...cle.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 ?
EnhanceIO was designed for and has been validated in enterprise environments. The important benefits are -
1. There is no downtime for cache creation, deletion, editing properties, writeback/readonly/writethrough mode change.
2. Wb mode comes with an option to control whether dirty data should be clean-up across reboots, which prevents SSD/HDD going out of sync.
3. Our in-house testing was done for large setups with 500GB+SSDs and proportionately large HDDs, on 24CPU machines with plenty of RAM. It's survived heavy IO loads without any locking or corruption problems.
4. Error handling is exactly what enterprises look for - writethrough/readonly modes work seamlessly regardless of SSD failures. In all the three caching modes, the guarantees of completion in presence of IO errors or shutdowns, in terms of granularity and persistence of data written, is identical to underlying HDDs.
5. It works for all known block devices - Software RAIDs, full block devices with or without partitions, individual partitions, various intelligent block devices.
-Amit
PROPRIETARY-CONFIDENTIAL INFORMATION INCLUDED
This electronic transmission, and any documents attached hereto, may contain confidential, proprietary and/or legally privileged information. The information is intended only for use by the recipient named above. If you received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of information received in error is strictly prohibited, and violators will be pursued legally.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists