From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is my system (really) using nptl
Date: Sun, 14 Oct 2012 21:19:47 +0200 [thread overview]
Message-ID: <507B1053.4090606@binarywings.net> (raw)
In-Reply-To: <CA+czFiAo9-cfZDxAZuqGcNJ55ieFqcG2r4_SD6z5mVU+5ndQVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
Am 14.10.2012 17:07, schrieb Michael Mol:
> On Sun, Oct 14, 2012 at 5:31 AM, Florian Philipp <lists@binarywings.net> wrote:
>> Am 14.10.2012 01:20, schrieb Michael Mol:
>>> On Sat, Oct 13, 2012 at 4:18 PM, Canek Peláez Valdés <caneko@gmail.com> wrote:
>>>> On Sat, Oct 13, 2012 at 2:50 PM, Michael Mol <mikemol@gmail.com> wrote:
>>>> [snip]
>>>>> (Well, I'm not certain that POSIX thinks of threads as parents to each other.
>>>>
>>>> Hence the reason I put "parent" in quotes, and I specified "actually,
>>>> the thread that created it".
>>>>
>>>>> There are *numerous* IPC mechanisms available on Linux. For starters,
>>>>> there are sockets (domain, IPv4, IPv6, et al), named pipes, signals,
>>>>> mmap()'d files, messaging, etc.
>>>>
>>>> Yeah, none of them "easy and quickly" to use, or at least not if you
>>>> compare it with shared memory.
>>>
>>> I assume you mean 'shared memory' in the 'many threads to an address
>>> space', not the /dev/shm sense.
>>>
>>
>> If we really want to be nit-picking, we have to assume 'shared memory'
>> as in malloc'ed [1] or stack memory. Anonymous mmap'ed memory mappings
>> are preserved across forks and changes in them can be shared since
>> kernel 2.4.
>
> Absolutely.
>
>> [1] Yes, I know that malloc uses mmap but its mappings are MAP_PRIVATE.
>
> For the GNU libc, yeah. I noticed that in strace, and was amused.
>
Huh? Are there other libcs that do it differently? I can't imagine any
alternative (except of the sbrk function from the bad old days).
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-10-14 19:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 13:24 [gentoo-user] Is my system (really) using nptl Timur Aydin
2012-10-12 17:46 ` Canek Peláez Valdés
2012-10-12 23:55 ` Volker Armin Hemmann
2012-10-13 0:09 ` Timur Aydin
2012-10-13 1:11 ` Mark Knecht
2012-10-13 11:15 ` Timur Aydin
2012-10-13 12:09 ` Volker Armin Hemmann
2012-10-13 16:15 ` Canek Peláez Valdés
2012-10-13 17:10 ` Mark Knecht
2012-10-13 18:16 ` Canek Peláez Valdés
2012-10-13 18:40 ` Mark Knecht
2012-10-13 18:57 ` Matthew Finkel
2012-10-13 19:00 ` Canek Peláez Valdés
2012-10-13 19:50 ` Michael Mol
2012-10-13 20:18 ` Canek Peláez Valdés
2012-10-13 23:20 ` Michael Mol
2012-10-14 9:31 ` Florian Philipp
2012-10-14 15:07 ` Michael Mol
2012-10-14 19:19 ` Florian Philipp [this message]
2012-10-14 19:30 ` Michael Mol
2012-10-14 19:35 ` [gentoo-user] " James
2012-10-14 20:05 ` [gentoo-user] " mike
2012-10-14 22:32 ` Volker Armin Hemmann
2012-10-13 20:13 ` Timur Aydin
2012-10-13 20:28 ` lists
2012-10-13 12:51 ` Michael Mol
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=507B1053.4090606@binarywings.net \
--to=lists@binarywings.net \
--cc=gentoo-user@lists.gentoo.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