All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: David Howells <dhowells@redhat.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<linux-fsdevel@vger.kernel.org>, Andrew Morton <akpm@digeo.com>
Subject: Re: [PATCH] General filesystem cache
Date: Fri, 18 Jul 2003 20:09:20 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0307182000300.6370-100000@home.osdl.org> (raw)
In-Reply-To: <23055.1058538289@warthog.warthog>


On Fri, 18 Jul 2003, David Howells wrote:
> 
> Here's a patch to add a quasi-filesystem ("CacheFS") that turns a block device
> into a general cache for any other filesystem that cares to make use of its
> facilities.
> 
> This is primarily intended for use with my AFS filesystem, but I've designed
> it such that it needs to know nothing about the filesystem it's backing, and
> so it may also be useful for NFS, SMB and ISO9660 for example.

Ok. Sounds good. In fact, it's something I've wanted for a while, since 
it's also potentially the solution to performance-critical things like 
virtual filesystems based on revision control logic etc (traditionally 
done with fake NFS servers).

I did a very very quick scan, and didn't see anything that raised my 
hackles. But it's late in the 2.6.x game, and as a result I'm not going to 
apply it until I get a lot of feedback from actual users too.

		Linus


       reply	other threads:[~2003-07-19  2:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <23055.1058538289@warthog.warthog>
2003-07-19  3:09 ` Linus Torvalds [this message]
2003-07-19  4:41   ` [PATCH] General filesystem cache David Chow
2003-07-20  9:29     ` David Howells
2003-07-19 14:59   ` Jeff Garzik
2003-07-20  9:30     ` David Howells
2003-07-20  9:28   ` David Howells
     [not found] <Pine.LNX.4.44.0307191157570.19755-100000@cpwright.com>
2003-07-20  9:38 ` David Howells
2003-07-31  6:31   ` Rob Landley

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=Pine.LNX.4.44.0307182000300.6370-100000@home.osdl.org \
    --to=torvalds@osdl.org \
    --cc=akpm@digeo.com \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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.