On 11/27/06, Eric Van Hensbergen <[EMAIL PROTECTED]> 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 sit
On Sat, 2006-12-02 at 13:28 -0500, Ming Zhao wrote:
> On 12/1/06, Ming Zhang <[EMAIL PROTECTED]> 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
On 12/1/06, Ming Zhang <[EMAIL PROTECTED]> 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
On Mon, 2006-11-27 at 13:55 -0600, Eric Van Hensbergen wrote:
> On 11/27/06, bert hubert <[EMAIL PROTECTED]> wrote:
> > On Mon, Nov 27, 2006 at 06:26:34PM +, Eric Van Hensbergen wrote:
> > > This is the first cut of a device-mapper target which provides a
> > > write-back
> > > or write-throug
On Friday 01 December 2006 08:16, Ming Zhao wrote:
> On 11/30/06, Jens Wilke <[EMAIL PROTECTED]> wrote:
> > - You don't keep track of I/O on the fly to the cache that is mapped
> > directly in cache_hit(). How do you make sure that this I/O is completed
> > before you replace a cache block?
>
> Th
On 11/30/06, Jens Wilke <[EMAIL PROTECTED]> wrote:
- You don't keep track of I/O on the fly to the cache that is mapped
directly in cache_hit(). How do you make sure that this I/O is completed
before you replace a cache block?
The previous I/O from cache hit and the later I/O for cache
replacem
On Thursday 30 November 2006 17:24, Eric Van Hensbergen wrote:
> On 11/30/06, Jens Wilke <[EMAIL PROTECTED]> wrote:
> > On Monday 27 November 2006 19:26, Eric Van Hensbergen wrote:
> >
> > If this is intended to speed up remote disks, is it possible that the cache
> > content
> > can be paged out
On 11/30/06, Jens Wilke <[EMAIL PROTECTED]> wrote:
On Monday 27 November 2006 19:26, Eric Van Hensbergen wrote:
If this is intended to speed up remote disks, is it possible that the cache
content
can be paged out on local disks in low-mem situations?
The main intent was to use local disks as
On Mon, Nov 27, 2006 at 06:26:34PM +, 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 i
On Monday 27 November 2006 19:26, 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
> clus
On 11/27/06, bert hubert <[EMAIL PROTECTED]> wrote:
On Mon, Nov 27, 2006 at 06:26:34PM +, 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 devi
On Mon, Nov 27, 2006 at 06:26:34PM +, 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 i
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.
In performance tests with iSCSI, gave peformance imp
13 matches
Mail list logo
