From: David Howells <dhowells@warthog.cambridge.redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: David Howells <dhowells@redhat.com>,
torvalds@transmeta.com, jgarzik@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: extra PG_* bits for page->flags
Date: Tue, 11 Feb 2003 10:54:44 +0000 [thread overview]
Message-ID: <29267.1044960884@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20030210151244.7e42d3fb.akpm@digeo.com>
Andrew Morton <akpm@digeo.com> wrote:
> > I'm writing a cache filesystem for primarily for caching AFS pages, but
> > that also can be used for caching other network FS pages (such as NFSv4,
> > which Jeff Garzik and Trond Myklebust are interested in, I think).
>
> Is a new fs needed? Is it not possible to use an existing filesystem of the
> user's choice for local caching?
The problem with that is who owns the pages being served? With an existing
filesystem either the pages have to belong to the cache FS (and not the net
FS) or double buffering has to be incurred.
What my FS strives to do is make it so the pages are owned by the net FS, the
cache FS just provides operations to perform reads/writes from/to disc to any
page (plus journalling).
The cache FS then only owns the pages which hold its metadata.
Also - though their may be ways around this according to Stephen Tweedie - the
handling of holes in files is different. In my cache FS, a hole as a page that
we don't have from the server yet. In an existing FS, a hole is a page of
zeros that simply doesn't reside on disc.
David
prev parent reply other threads:[~2003-02-11 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 10:51 extra PG_* bits for page->flags David Howells
2003-02-10 23:12 ` Andrew Morton
2003-02-11 0:07 ` Nigel Cunningham
2003-02-11 0:20 ` Andrew Morton
2003-02-11 2:17 ` Nigel Cunningham
2003-02-11 4:18 ` Valdis.Kletnieks
2003-02-11 11:05 ` David Howells
2003-02-11 10:54 ` David Howells [this message]
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=29267.1044960884@warthog.cambridge.redhat.com \
--to=dhowells@warthog.cambridge.redhat.com \
--cc=akpm@digeo.com \
--cc=dhowells@redhat.com \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox