All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Eric Van Hensbergen <ericvh@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: Device Mapper as a cache for SAN?
Date: Mon, 10 Apr 2006 20:35:44 -0400	[thread overview]
Message-ID: <1144715744.8591.197.camel@localhost.localdomain> (raw)
In-Reply-To: <a4e6962a0604101728o42596adaldb5a2ceb9348f37e@mail.gmail.com>

On Mon, 2006-04-10 at 19:28 -0500, Eric Van Hensbergen wrote:
> On 4/10/06, Ming Zhang <mingz@ele.uri.edu> wrote:
> > On Mon, 2006-04-10 at 14:46 -0500, Eric Van Hensbergen wrote:
> > > On 4/10/06, Ed Wilts <ewilts@ewilts.org> wrote:
> > > >
> > > > The obvious question is why?  What would this provide that the kernel
> > > > and file systems don't already provide?
> > > >
> > >
> > > Well, kernel provides in-memory page cache, not local disk page cache.
> > >  There is some ongoing remote file system local disk cache work being
> > > done, but it applies primarily to AFS and NFS - not block-based
> > > transports such as iSCSI and AOE.  The various cluster file systems
> > > may provide something more akin to this, but again, this doesn't
> > > really cover SAN technologies -- not in any sort of a generic way.
> > > Let me know if I'm missing something.
> >
> > still, what is the main benefit of this cache? what u mean "local disk
> > page cache"? use "local disk" as page cache or page cache for "local
> > disk" or something else?
> >
> 
> Okay, I suppose I wasn't exactly clear.  What I want is something that
> will let me use a local disk (or local disks) as a cache for a storage
> area network volume (or volumes).  There are a variety of scenarios -

so a disk as cache for another (remote) disk(s).

> my primary interest is in using it for large clusters with shared
> read-only volumes or with exclusive-access read/write volumes.   So,
> local disk page cache is probably not the right terminology -- it is
> simply a local block cache for a remote block device.

yes, "page cache" has its meaning in linux.

as i know, no stable implementation for this.

> 
>        -eric

  reply	other threads:[~2006-04-11  0:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 17:58 Device Mapper as a cache for SAN? Eric Van Hensbergen
2006-04-10 18:45 ` Ed Wilts
2006-04-10 19:46   ` Eric Van Hensbergen
2006-04-10 21:25     ` Ming Zhang
2006-04-11  0:28       ` Eric Van Hensbergen
2006-04-11  0:35         ` Ming Zhang [this message]
2006-04-11  0:47           ` Eric Van Hensbergen
2006-04-11  0:50             ` Ming Zhang
2006-04-11  8:55       ` Jure Pečar
2006-04-11 12:57         ` Ming Zhang
2006-04-10 22:22     ` Artur Bergman

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=1144715744.8591.197.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=dm-devel@redhat.com \
    --cc=ericvh@gmail.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.