From: Daniel Phillips <phillips@bonn-fries.net>
To: hunghochak@netscape.net (Ho Chak Hung), linux-kernel@vger.kernel.org
Subject: Re: Using page cache without a file system
Date: Fri, 22 Jun 2001 14:49:42 +0200 [thread overview]
Message-ID: <01062214494203.00455@starship> (raw)
In-Reply-To: <72AE45C3.2DE2C328.0F76C228@netscape.net>
In-Reply-To: <72AE45C3.2DE2C328.0F76C228@netscape.net>
On Friday 22 June 2001 05:33, Ho Chak Hung wrote:
> Is it possible to allocate and add pages to the page cache without a
> underlying file system in Linux 2.4? I know that the host pointer to inode
> structure inside the address_space structure can be NULL, but does this
> mean that we can still make use of page cache operations like readpage or
> writepage if we do not back up the cache with a file system? I am currently
> developing a driver that wants to make use of the page cache, however, I
> want to save myself with the heavy load of kmalloc.
>
> Any hint would be greatly appreciated.
Check out ramfs
--
Daniel
prev parent reply other threads:[~2001-06-22 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 3:33 Using page cache without a file system Ho Chak Hung
2001-06-22 12:49 ` Daniel Phillips [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=01062214494203.00455@starship \
--to=phillips@bonn-fries.net \
--cc=hunghochak@netscape.net \
--cc=linux-kernel@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 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).