From: Hugh Dickins <hugh@veritas.com>
To: Kurt Wall <kwall@kurtwerks.com>
Cc: "Gábor Lénárt" <lgb@lgb.hu>,
"Arjan van de Ven" <arjan@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: OT: fork(): parent or child should run first?
Date: Thu, 12 Jan 2006 17:23:48 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0601121719550.9759@goblin.wat.veritas.com> (raw)
In-Reply-To: <20060112013858.GB6178@kurtwerks.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 815 bytes --]
On Wed, 11 Jan 2006, Kurt Wall wrote:
> On Wed, Jan 11, 2006 at 02:02:55PM +0100, Gábor Lénárt took 0 lines to write:
> >
> > Ok, you're absolutly right here. My problem is to find some solution and not
> > to change the behaviour of fork() of course :) It's quite annoying to
> > introduce some kind of IPC between parent and childs just for transferring a
> > single pid_t ;-) Using exit status would be great (I would transfer "n")
>
> But IPC, especially shared memory, would be great for this if you can
> set up the shmid ahead of time. It would certainly be fast.
I've not been following the thread, but if your suggestion is good, then
better would be to use mmap MAP_SHARED|MAP_ANONYMOUS - that gives memory
shared between parent and children, without all the nuisance of shmids.
Hugh
next prev parent reply other threads:[~2006-01-12 17:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 12:37 Gábor Lénárt
2006-01-11 12:51 ` Arjan van de Ven
2006-01-11 13:02 ` Gábor Lénárt
2006-01-11 13:25 ` Bernd Petrovitsch
2006-01-11 13:49 ` Ian Campbell
2006-01-11 13:55 ` Bernd Petrovitsch
2006-01-11 14:05 ` Ian Campbell
2006-01-11 15:19 ` linux-os (Dick Johnson)
2006-01-12 1:33 ` David Schwartz
2006-01-12 1:38 ` Kurt Wall
2006-01-12 17:23 ` Hugh Dickins [this message]
2006-01-12 20:19 ` Gábor Lénárt
2006-01-11 13:34 ` Roland Kuhn
2006-01-11 17:11 ` Lee Revell
2006-01-11 13:03 ` Miquel van Smoorenburg
2006-01-11 13:08 ` Jan-Benedict Glaw
2006-01-12 1:33 ` David Schwartz
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=Pine.LNX.4.61.0601121719550.9759@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=arjan@infradead.org \
--cc=kwall@kurtwerks.com \
--cc=lgb@lgb.hu \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®