All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaya Potter <spotter@cs.columbia.edu>
To: linux-fsdevel@vger.kernel.org
Subject: using page cache directly?
Date: Fri, 21 Nov 2003 15:04:37 -0500	[thread overview]
Message-ID: <3FBE6FD5.6080502@cs.columbia.edu> (raw)

I'm trying to write a stackable file system that supports branching 
(i.e. mount time options of old_branch and new_branch).  In order to do 
it, I need to version the directories as well, what I'd like to do is 
have a file act as the directory (basically ";branch" on the underlying 
fs inside the right dir) which will just map "Stacked Filename" to 
"underlying filename".  If I were doing it in user space, I'd just mmap 
the file, and deal with it directly like that, but as I understand it's 
not really appropriate to do that inside the kernel (and only possible 
w/ vmalloc'd pages).  The correct way (I was told) is to use the page 
cache.  As don't have a lot of experience with that, can someone point 
me in the right direction so I can learn to deal w/ it.

thanks,

shaya


             reply	other threads:[~2003-11-21 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21 20:04 Shaya Potter [this message]
2003-11-21  9:00 ` using page cache directly? Joseph D. Wagner
2003-11-21 21:10   ` Pat LaVarre

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=3FBE6FD5.6080502@cs.columbia.edu \
    --to=spotter@cs.columbia.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    /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.