public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: safemode <safemode@speakeasy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question about tmpfs
Date: 17 Aug 2001 10:18:46 +0200	[thread overview]
Message-ID: <m34rr79k0p.fsf@linux.local> (raw)
In-Reply-To: <20010817064809Z269735-760+2777@vger.kernel.org>
In-Reply-To: <20010817064809Z269735-760+2777@vger.kernel.org>

On Fri, 17 Aug 2001, safemode@speakeasy.net wrote:
> I looked in the documentation for something about tmpfs and looked
> around for some obvious tmpfs source but couldn't find any to figure
> out how to know when/if it's doing what it's supposed to.  when i ls
> the dir it's mounted to i get nothing and this is what df gives me.
> Filesystem           1k-blocks    Used    Available Use% Mounted on
> tmpfs                   144108        0        144108       0%       /dev/shm

In the 2.3 timeframe SYSV shared memory did require you to mount shmfs
somewhere to work properly. This was relaxed since Al Viro introduced
kernel internal mount points. This feature is used now for SYSV shm
and shared anonymous maps. You do not see this instance in user
space. You can use ipcs to show the SYSV segmants.

The instance on /dev/shm only used by the shmopen/shmunlink functions
of glibc 2.2. These functions are specified by POSIX for shared memory
handling. Since there aren't a lot of programs using this interface
right now, you do not see anything here and could drop this mount from
your fstab. But if you use such a program you will need a tmpfs
instance mounted somewhere (preferably under /dev/shm).

Greetings
		Christoph



      reply	other threads:[~2001-08-17  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17  6:48 question about tmpfs safemode
2001-08-17  8:18 ` Christoph Rohland [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=m34rr79k0p.fsf@linux.local \
    --to=cr@sap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=safemode@speakeasy.net \
    /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