From: "Hesse, Christian" <mail@earthworm.de>
To: Indrek Kruusa <indrek.kruusa@tuleriit.ee>
Subject: Re: [QUESTION] Filesystem like structure in RAM w/o using filesystem (not ramdisk)
Date: Thu, 1 Dec 2005 13:20:02 +0100
User-Agent: KMail/1.9
Cc: linux-kernel@vger.kernel.org
References: <438EE256.6040403@tuleriit.ee>
In-Reply-To: <438EE256.6040403@tuleriit.ee>
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart1803321.rHgT44oBQo";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200512011320.10092.mail@earthworm.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1185
Lines: 37

--nextPart1803321.rHgT44oBQo
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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.
=2D-=20
Christian

--nextPart1803321.rHgT44oBQo
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.9.19 (GNU/Linux)

iD8DBQBDjup6lZfG2c8gdSURAl28AKD7MRfyoehpNaVrXBEBvto0B8TSIgCg7Zn9
f8+GcrE3l2X/inTxgnbS6fY=
=n7bq
-----END PGP SIGNATURE-----

--nextPart1803321.rHgT44oBQo--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/