From: Christoph Rohland <hans-christoph.rohland@sap.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: MM mailing list <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.rutgers.edu>,
"Eric W. Biederman" <ebiederm+eric@ccr.net>,
Alexander Viro <viro@math.psu.edu>,
GOTO Masanori <gotom@debian.or.jp>
Subject: Re: [PATCH] replace SYSV shared memory with shm filesystem
Date: 10 Jan 2000 13:46:22 +0100 [thread overview]
Message-ID: <qwwpuvart5t.fsf@sap.com> (raw)
In-Reply-To: Alan Cox's message of "Mon, 10 Jan 2000 12:39:50 +0000 (GMT)"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > replaces/reuses the existing SYSV shm code so you now have to
> > mount the fs to be able to use SYSV SHM. But in turn we now have
> > everything in place to implement posix shm. This also obsoletes
> > vm_private_data in vm_area_struct.
>
> Umm no. It obsoletes vm_private_data for existing merged file
> systems. The stackable file systems still need this field (cryptfs,
> lofs etc)
Hey, that's a pity :-( I liked this cleanup. Do they really need it?
> > Also it is now possible to do e.g. 'rm /dev/shm/*' instead of this
> >terrible 'ipcrm shm xx' :-)
>
> Nice
Yup :-)
Greetings
Christoph
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.nl.linux.org/Linux-MM/
next prev parent reply other threads:[~2000-01-10 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-10 12:17 Christoph Rohland
2000-01-10 12:39 ` Alan Cox
2000-01-10 12:46 ` Christoph Rohland [this message]
2000-01-10 12:52 ` Rik van Riel
2000-01-10 13:59 ` Andi Kleen
2000-01-10 17:55 ` Christoph Rohland
2000-01-10 20:41 ` James Antill
2000-01-11 11:18 ` Richard Guenther
2000-01-11 12:00 ` 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=qwwpuvart5t.fsf@sap.com \
--to=hans-christoph.rohland@sap.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm+eric@ccr.net \
--cc=gotom@debian.or.jp \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=viro@math.psu.edu \
/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