public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Manfred <mx2927@gmail.com>
To: libc-help@sourceware.org
Cc: Florian Weimer <fweimer@redhat.com>
Subject: Re: What is the point of IPC_PRIVATE of shmget?
Date: Mon, 12 Apr 2021 19:55:30 +0200	[thread overview]
Message-ID: <9653dac2-7c03-cad0-34fa-94d0101165d8@gmail.com> (raw)
In-Reply-To: <87sg3viio7.fsf@oldenburg.str.redhat.com>



On 4/12/2021 6:14 PM, Florian Weimer via Libc-help wrote:
> * Peng Yu:
> 
>> On Mon, Apr 12, 2021 at 11:07 AM Florian Weimer <fweimer@redhat.com> wrote:
>>>
>>> * Peng Yu via Libc-help:
>>>
>>>> I don't get the point of IPC_PRIVATE of shmget(). Since it is just
>>>> used by the current process, why not just use malloc?
>>>>
>>>> Can anybody give a real example in which IPC_PRIVATE must be used, but
>>>>   malloc or other variant of *alloc functions are not appropriate to
>>>> use? Thanks.
>>>
>>> shmget(2) says this:
>>>
>>> | BUGS
>>> |        The name choice IPC_PRIVATE was perhaps unfortunate, IPC_NEW
>>> |        would more clearly show its function.
>>>
>>> Does this answer your question?
>>
>> No. That is just a naming issue. It is still privately used by the
>> current process instead of other processes.
> 
> Oh, it can be shared if the process forks.  With malloc, you'd lose the
> sharing.

Out of curiosity,
Does it need to fork? Can the identifier be shared in some other way?

Thanks,
Manfred

> 
> Thanks,
> Florian
> 

  parent reply	other threads:[~2021-04-12 17:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 15:54 Peng Yu
2021-04-12 16:06 ` tomas
2021-04-12 16:07 ` Florian Weimer
2021-04-12 16:12   ` Peng Yu
2021-04-12 16:14     ` Florian Weimer
2021-04-12 16:18       ` Florian Weimer
2021-04-12 17:23       ` Peng Yu
2021-04-12 18:17         ` J Lumby
2021-04-12 17:55       ` Manfred [this message]
2021-04-12 19:05         ` Peng Yu

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=9653dac2-7c03-cad0-34fa-94d0101165d8@gmail.com \
    --to=mx2927@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-help@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).