linux-kernel - Re: [RFC][PATCH] dm-cache: block level disk cache target for device mapper

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061127184748.GA11219@outpost.ds9a.nl>
Date:	Mon, 27 Nov 2006 19:47:48 +0100
From:	bert hubert <bert.hubert@...herlabs.nl>
To:	Eric Van Hensbergen <ericvh@...a.kernel.org>
Cc:	linux-kernel@...r.kernel.org, dm-devel@...hat.com,
	ming@...s.ufl.edu, ericvh@...il.com
Subject: Re: [RFC][PATCH] dm-cache: block level disk cache target for device mapper

On Mon, Nov 27, 2006 at 06:26:34PM +0000, Eric Van Hensbergen wrote:
> This is the first cut of a device-mapper target which provides a write-back
> or write-through block cache.  It is intended to be used in conjunction with
> remote block devices such as iSCSI or ATA-over-Ethernet, particularly in
> cluster situations.

How does this work in practice? In other words, what is a typical actual
configuration?

There is a remote block device, and a local one, and these are kept into
sync in some way?

Thanks.

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services
-
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/