archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <>
To: David Howells <>,
	"Charles P. Wright" <>
Cc: David Howells <>,,
Subject: Re: [PATCH] General filesystem cache
Date: Thu, 31 Jul 2003 02:31:54 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <17869.1058693883@warthog.warthog>

On Sunday 20 July 2003 05:38, David Howells wrote:
> > Is this patch available from somewhere?  I looked on the MARC archives
> > but haven't been able to find the original mail which includes the patch.
> I don't know. The message containing the patches doesn't seem to have made
> it into either the LKML or the linux-fsdevel mailing lists.
> The basic code can be found in:
> In directories:
> 	Documentations/filesystems/
> 	include/linux/
> 	fs/cachefs/
> I'll see about putting the patch up for download when I get to OLS.
> David

Random question:

Way back when I used union mount code (under OS/2) that would mount the first 
filesystem read-only, and allow you to cache changes to it in a second 
filesystem.  (So you could do a build of slightly self-modifying code, a lot 
like the Linux build in 2.4 was, against a read-only tree.) 

Would this be a good tool for that sort of application?  (There's all sorts of 
other "trial run" type applications; running stuff against database snapshots 
and then seeing what the deltas are, etc...)


  reply	other threads:[~2003-07-31  6:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2003-07-20  9:38 ` [PATCH] General filesystem cache David Howells
2003-07-31  6:31   ` Rob Landley [this message]
     [not found] <23055.1058538289@warthog.warthog>
2003-07-19  3:09 ` Linus Torvalds
2003-07-19  4:41   ` 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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).