From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Mai Daftedar <mai.daftedar@gmail.com>
Cc: linux-kernel@vger.kernel.org, clemens@ladisch.de
Subject: Re: Inter Thread Coomunication
Date: Wed, 02 Dec 2009 18:19:45 +0100 [thread overview]
Message-ID: <4B16A1B1.9010101@s5r6.in-berlin.de> (raw)
In-Reply-To: <2cd4ff050912020417r27b52a89v4e676c7d4ab74ad4@mail.gmail.com>
Mai Daftedar wrote:
> After some googling I learnt that using queues and pipes are expensive
> (effieciency wise) and that I should just pass in the parameters and
> use mutex to protect shared data...
> Can anyone add on to this tradeoff information
The entire point of threads (in contrast to processes) is to share an
address space for convenience or/and performance. If a shared address
space is not really required, separate processes could be used instead
with the huge advantage of memory protection.
--
Stefan Richter
-=====-==--= ==-- ---=-
http://arcgraph.de/sr/
prev parent reply other threads:[~2009-12-02 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 12:17 Mai Daftedar
2009-12-02 12:36 ` Clemens Ladisch
2009-12-02 17:19 ` Stefan Richter [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=4B16A1B1.9010101@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mai.daftedar@gmail.com \
/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®