| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4BE0B225.2080308@gmail.com> Date: Tue, 04 May 2010 15:47:49 -0800 From: Kent Overstreet <kent.overstreet@...il.com> To: Andi Kleen <andi@...obates.de> CC: linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/3] Bcache: version 4 On 05/04/2010 02:14 AM, Andi Kleen wrote: > I read all of this email now and I still have no clue what exactly > a 'bcache' is and why anyone would want one (and if one needs > a large stick to handle it or not) > > Normally the 0/x series of a patch kit is supposed to contain that > information. > > I know it's probably obvious to you, but it's not to most other readers. > > Consider adding some introduction? Ah, whoops. "Block cache" - it uses one block device to cache another, it's intended for SSDs. It's summarized decently in the documentation patch, which if I'd thought harder would've been the first email... http://thread.gmane.org/gmane.linux.kernel/979977 Second patch also has relevant commentary: http://thread.gmane.org/gmane.linux.kernel/979978 http://thread.gmane.org/gmane.linux.kernel/979979 Currently all the necessary functionality for read only is close to done, I'm now doing stress testing. I'm hoping to have it Stable For Me and read/write done in a week or two, at which point it should be ready for people to start playing with. -- 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