From: Christoph Rohland <hans-christoph.rohland@sap.com>
To: Kanoj Sarcar <kanoj@google.engr.sgi.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.rutgers.edu,
torvalds@transmeta.com
Subject: Re: [RFC] [RFT] Shared /dev/zero mmaping feature
Date: 29 Feb 2000 11:54:36 +0100 [thread overview]
Message-ID: <qwwem9wnus3.fsf@sap.com> (raw)
In-Reply-To: kanoj@google.engr.sgi.com's message of "Fri, 25 Feb 2000 15:08:49 -0800 (PST)"
Hi Kanoj,
kanoj@google.engr.sgi.com (Kanoj Sarcar) writes:
> This is a patch against 2.3.47 that tries to implement shared /dev/zero
> mappings. This is just a first cut attempt, I am hoping I will find a
> few people to apply the patch and throw some real life programs at it
> (preferably on low memory machines so that swapping is induced).
>
> Currently, you will also need to turn on CONFIG_SYSVIPC, but most of
> the shm.c code can be split into a new ipc/shm_core.c file that is
> always compiled in, irrespective of CONFIG_SYSVIPC. Linus, do you
> think this is the proper direction to follow?
>
> Thanks. Comments and feedback welcome ...
Why do you use this special zero_id stuff? It clutters up the whole
code.
If you would simply open a normal shm segment with key IPC_PRIVATE and
directly remove it nobody can attach to it and it will be released on
exit and everything. No special handling needed any more. BTW that's
exectly what we do in user space to circumvent the missing MAP_ANON |
MAP_SHARED.
I would also prefer to be able to see the allocated segments with the
ipc* commands.
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.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-02-29 10:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-25 23:08 Kanoj Sarcar
2000-02-26 16:38 ` Linus Torvalds
2000-02-26 21:47 ` Kanoj Sarcar
2000-02-29 10:54 ` Christoph Rohland [this message]
2000-02-29 18:30 ` Kanoj Sarcar
2000-03-01 12:08 ` Christoph Rohland
2000-03-01 17:34 ` Kanoj Sarcar
2000-03-01 17:55 ` Christoph Rohland
2000-03-01 18:18 ` Kanoj Sarcar
2000-03-01 19:42 ` Christoph Rohland
2000-03-01 20:09 ` Kanoj Sarcar
2000-03-06 22:43 ` Stephen C. Tweedie
2000-03-06 23:01 ` Kanoj Sarcar
2000-03-08 12:02 ` Christoph Rohland
2000-03-08 17:51 ` Kanoj Sarcar
2000-03-08 18:35 ` Christoph Rohland
2000-03-08 18:48 ` Linus Torvalds
2000-03-08 18:57 ` Kanoj Sarcar
2000-03-09 18:15 ` 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=qwwem9wnus3.fsf@sap.com \
--to=hans-christoph.rohland@sap.com \
--cc=kanoj@google.engr.sgi.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.com \
/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