From: Christoph Rohland <hans-christoph.rohland@sap.com>
To: Alexander Viro <viro@math.psu.edu>, haible@ilog.fr
Cc: Linux Kernel Mailing List <linux-kernel@vger.rutgers.edu>
Subject: Re: [RFC] mapping parts of shared memory
Date: 03 Dec 1999 09:10:12 +0100 [thread overview]
Message-ID: <qwwg0xko36j.fsf@sap.com> (raw)
In-Reply-To: viro@math.psu.edu's message of "2 Dec 1999 22:47:04 +0100"
viro@math.psu.edu (Alexander Viro) writes:
> On Thu, 2 Dec 1999, Bruno Haible wrote:
>
> > 5) Use the proc filesystem. Implement a file /proc/ipc/shm/42 as being
> > equivalent to the shared memory segment with id 42.
> > File type: regular file
> > File size: the shm segment's size
> > File contents (for use by read, write, mmap): the shm segment's data
> > File owner/group: the shm segment's owner and group
> > truncate(): return -EINVAL
> >
> > Not only would this solve your "mmap of shared memory" problem, it would
> > become possible to view and edit shared memory using "cat", "hexdump" and
> > "vi". Benefits of the "everything is a file" philosophy.
>
> Don't do it in procfs. Make a separate filesystem and mount it on the
> empty directory in /proc, if you really need it (I'ld rather use some
> other location - even /dev/shm would be better). This filesystem will have
> _nothing_ with proc in terms of code. There is enough mess in procfs
> already. Keep this one separate.
I totally agree. After looking at the shm code I concluded that making
a filesystem out of it will cleanup the code a lot. There is much
duplication of code from the mm layer.
I am just working on this filesystem.
Greetings
Christoph
--
Christoph Rohland
SAP AG
LinuxLab Email: hans-christoph.rohland@sap.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-12-03 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-02 20:52 [RFC] mapping parts of shared memory Bruno Haible
1999-12-02 21:18 ` Alexander Viro
1999-12-03 8:10 ` Christoph Rohland [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-11-25 13:58 Christoph Rohland
1999-11-25 19:14 ` Kanoj Sarcar
1999-11-26 15:33 ` 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=qwwg0xko36j.fsf@sap.com \
--to=hans-christoph.rohland@sap.com \
--cc=haible@ilog.fr \
--cc=linux-kernel@vger.rutgers.edu \
--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 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.