All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: aeb@veritas.com (Andries Brouwer),
	marcelo@conectiva.com.br (Marcelo Tosatti),
	torvalds@transmeta.com (Linus Torvalds),
	linux-kernel@vger.kernel.org, gilbertd@treblig.org (Dave Gilbert)
Subject: Re: [Patch] shmmin behaviour back to 2.2 behaviour
Date: 28 Dec 2000 23:13:55 +0100	[thread overview]
Message-ID: <m3hf3ourke.fsf@linux.local> (raw)
In-Reply-To: <E14BfJ6-0003qw-00@the-village.bc.nu>

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> There are fundmental things shm* can do that mmap cannot. Does posix
> shm handle those (leaving segments alive but unattached being the
> obvious one)

Yes:
        shmget           == shm_open (+ ftruncate(fd, size))
        shmat            == mmap (0, size, , , fd, 0)
        shmdt            == munmap (addr, size);
        shmctl(IPC_RMID) == shm_unlink ()
        shmctl(IPC_STAT) == fstat();
        shmctl(IPC_LOCK) == mlock() /*nearly*/
        shmctl(IPC_SET)  == fchown(), fchmod()

You can get the Linux special behaviour to be able to attach to a
removed segment by its shmid by passing the file descriptor for the
posix shm from the attached process to the attaching process.

Did I miss something?
                        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:[~2000-12-28 22:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27 10:32 [Patch] shmmin behaviour back to 2.2 behaviour Christoph Rohland
2000-12-27 11:58 ` Dave Gilbert
2000-12-27 15:37   ` Christoph Rohland
2000-12-27 15:16 ` Marcelo Tosatti
2000-12-27 17:54   ` Christoph Rohland
2000-12-27 20:57   ` Andries Brouwer
2000-12-28 12:01     ` Christoph Rohland
2000-12-28 13:34       ` Andries Brouwer
2000-12-28 15:49         ` Alan Cox
2000-12-28 22:13           ` Christoph Rohland [this message]
2000-12-28 22:19             ` Alan Cox

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=m3hf3ourke.fsf@linux.local \
    --to=cr@sap.com \
    --cc=aeb@veritas.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gilbertd@treblig.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --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 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.