From: "Hesse, Christian" <mail@earthworm.de>
To: Indrek Kruusa <indrek.kruusa@tuleriit.ee>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [QUESTION] Filesystem like structure in RAM w/o using filesystem (not ramdisk)
Date: Thu, 1 Dec 2005 13:20:02 +0100 [thread overview]
Message-ID: <200512011320.10092.mail@earthworm.de> (raw)
In-Reply-To: <438EE256.6040403@tuleriit.ee>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
On Thursday 01 December 2005 12:45, Indrek Kruusa wrote:
> Hello!
>
> As I have understood the accessing ramdisk goes through the same kernel
> path which is meant for accessing slow block device (i_nodes caching etc.).
> Is there any other common way (some API above shared memory?) to
> create/open/read/write globally accessible hierarchical datablocks in RAM?
> Could it be possibly faster than ramdisk?
You should take a look at tmpfs, I think that is what you search for.
--
Christian
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2005-12-01 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 11:45 [QUESTION] Filesystem like structure in RAM w/o using filesystem (not ramdisk) Indrek Kruusa
2005-12-01 12:20 ` Hesse, Christian [this message]
2005-12-01 12:57 ` Bernd Eckenfels
2005-12-05 0:39 ` Rob Landley
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=200512011320.10092.mail@earthworm.de \
--to=mail@earthworm.de \
--cc=indrek.kruusa@tuleriit.ee \
--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 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.