linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: [Re: Process creating]
Date: Sat, 30 Jun 2001 12:32:47 +0200	[thread overview]
Message-ID: <20010630123247.C898@vagabond> (raw)
In-Reply-To: <20010627063513.18205.qmail@nw171.netaddress.usa.net>

On Wed, Jun 27, 2001 at 12:35:13AM -0600, Blesson Paul wrote:
> 1: P1 and P2 have different physical areas of memory. This is how 
> protection works.
> 
> 2: Why do they need to share the same memory? You can have your second
> process
> communicate with your first process through IPC.
> 
> 3: Linux supports threading if you include the thread library, and use the 
> appropriate
> threading process calls.
> 
> Another thing you can do is have a common space on the hard drive. It's not 
> as fast as RAM,
> but it's one solution.

As to 1 (and 3), if you clone the processes (using the __clone - advanced
version of fork), you can specify what the processes should share. Including
memory. Thus you can also have threads (that share everything but stack) even
without a thread library (libpthread actualy does just that, but it has some
conveniece stuff like locks).

As of 2, avoid using ipc, especialy the sysv one - it's rather kind
of crap (IMHO).

-------------------------------------------------------------------------------
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

      reply	other threads:[~2001-06-30 10:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-27  6:35 [Re: Process creating] Blesson Paul
2001-06-30 10:32 ` Jan Hudec [this message]

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=20010630123247.C898@vagabond \
    --to=bulb@ucw.cz \
    --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;
as well as URLs for NNTP newsgroup(s).