All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: "H . Peter Anvin" <hpa@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] tmpfs for 2.4.1
Date: 03 Feb 2001 16:02:27 +0100	[thread overview]
Message-ID: <m3zog3omik.fsf@linux.local> (raw)
In-Reply-To: <20010123205315.A4662@werewolf.able.es> <m3lmrqrspv.fsf@linux.local> <95csna$vb6$1@cesium.transmeta.com> <m3puh1que4.fsf@linux.local> <20010202215254.C2498@werewolf.able.es> <3A7B1EDC.DA2588BA@transmeta.com> <20010203010649.E3014@werewolf.able.es>
In-Reply-To: <20010203010649.E3014@werewolf.able.es>

"J . A . Magallon" <jamagallon@able.es> writes:

> I did not get the chance to deal too much with it, but apart from moving
> functionality from userspace (ipcs) to kernel (ls), what were/could be the
> benefits of /dev/shm ?. Can you create a shared memory segment by simply
> creating a file there, or it is just a picture of what is in kernelspace?.

The most appealing thing to me was rm -f /dev/shm/.IPC* :-) So I
should make a patch to ipcrm to allow multiple segments (and
wildcards?).

You could not create SYSV shm segments with open, but you could delete
them with rm and list the with ls.

> First time I saw that I thought: what could happen if /dev/shm is shared
> in a cluster ? or, lets suppose that /dev/shm is a logical volume made by
> addition of some nfs mounted volumes, one of each node, so one piece of
> the shm fs is local and other remote...kinda DSM/NUMA...?

No, this was never possible. It was only a fs interface to local
kernel objects (and still is).

> (just too much marijuana late at night...)

Oh, you are allowed to dream ;-)

Greetings
                Christoph

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

  reply	other threads:[~2001-02-03 14:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-23 19:53 swapfs for 2.4.1-pre J . A . Magallon
2001-02-01 21:39 ` [patch] tmpfs for 2.4.1 Christoph Rohland
2001-02-01 23:50   ` H. Peter Anvin
2001-02-02  9:57     ` Christoph Rohland
2001-02-02 20:52       ` J . A . Magallon
2001-02-02 20:55         ` H. Peter Anvin
2001-02-03  0:06           ` J . A . Magallon
2001-02-03 15:02             ` Christoph Rohland [this message]
2001-02-03 14:28           ` Christoph Rohland
2001-02-03 20:27             ` H. Peter Anvin
2001-02-03 20:46               ` J . A . Magallon
2001-02-04  9:53                 ` Christoph Rohland
2001-02-04  9:18               ` Christoph Rohland
     [not found]   ` <20010203234550.A507@squish>
     [not found]     ` <m3zog2n6ec.fsf@linux.local>
     [not found]       ` <20010205210540.A10316@squish>
2001-02-06  9:18         ` VM question (ramfs abuse) Christoph Rohland

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=m3zog3omik.fsf@linux.local \
    --to=cr@sap.com \
    --cc=hpa@transmeta.com \
    --cc=jamagallon@able.es \
    --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.