public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@warthog.cambridge.redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@digeo.com>,
	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 11:05:18 +0000	[thread overview]
Message-ID: <29336.1044961518@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <200302110418.h1B4I5jB002548@turing-police.cc.vt.edu>


Valdis.Kletnieks@vt.edu wrote:
> > Is a new fs needed?  Is it not possible to use an existing filesystem of
> > the user's choice for local caching?
> 
> It's sort of like a loopback mount - you need a backing store which could be
> on an ext3 or ramfs or whatever, and you need the user-visible front end
> side of things, which manages the backing store and fetches blocks from
> AFS/NFS/etc.

Sort of, yes. Making it a filesystem is more a way of making it possible for
the kernel to associate a block device directly with the caching code. Rather
than adding an additional kernel interface beyond mount/swapon, you can just
use mount to add a block device to the cache.

Furthermore, it meand that I can provide virtual files along the lines of
/proc in the mountpoint that allow you to access status information, and maybe
also control the data cached.

David

  reply	other threads:[~2003-02-11 10:57 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 [this message]
2003-02-11 10:54   ` 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:
  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=29336.1044961518@warthog.cambridge.redhat.com \
    --to=dhowells@warthog.cambridge.redhat.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --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