All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'andrebalsa@altern.org'" <andrebalsa@altern.org>,
	"'Richard E. Gooch'" <rgooch@atnf.csiro.au>,
	"'Ingo Molnar'" <mingo@elte.hu>,
	"'rml@tech9.net'" <rml@tech9.net>,
	"'akpm@osdl.org'" <akpm@osdl.org>
Subject: Re: Linux scheduler (scheduling)  questions
Date: Tue, 29 Jun 2004 17:17:13 +0200	[thread overview]
Message-ID: <1088522233.1709.2.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <313680C9A886D511A06000204840E1CF08F42FA3@whq-msgusr-02.pit.comms.marconi.com>

On Tue, 2004-06-29 at 08:51 -0400, Povolotsky, Alexander wrote:

> 5. Deviating from the scheduling line of questions (but staying with threads
> issues): is there an option in clone(2)  to make threads 
>    not to run in the same  address space but rather act as independent
> process(es).

If you want something in a different address space, then you want a
process. Threads of the same process share the whole address space
(except they have their own stack) and this have some advantages, like
faster CPU context switching between threads of the same process, and
faster creation times, among others.



  reply	other threads:[~2004-06-29 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 12:51 Linux scheduler (scheduling) questions Povolotsky, Alexander
2004-06-29 15:17 ` Felipe Alfaro Solana [this message]
2004-06-29 22:52 ` Con Kolivas

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=1088522233.1709.2.camel@teapot.felipe-alfaro.com \
    --to=felipe_alfaro@linuxmail.org \
    --cc=Alexander.Povolotsky@marconi.com \
    --cc=akpm@osdl.org \
    --cc=andrebalsa@altern.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rgooch@atnf.csiro.au \
    --cc=rml@tech9.net \
    /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.