Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932174AbVLALp1 (ORCPT ); Thu, 1 Dec 2005 06:45:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932173AbVLALp1 (ORCPT ); Thu, 1 Dec 2005 06:45:27 -0500 Received: from www.stv.ee ([212.7.5.251]:59407 "EHLO www.stv.ee") by vger.kernel.org with ESMTP id S932174AbVLALp1 (ORCPT ); Thu, 1 Dec 2005 06:45:27 -0500 Message-ID: <438EE256.6040403@tuleriit.ee> Date: Thu, 01 Dec 2005 13:45:26 +0200 From: Indrek Kruusa User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: [QUESTION] Filesystem like structure in RAM w/o using filesystem (not ramdisk) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 612 Lines: 16 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? Thanks in advance, Indrek - 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/