linux-kernel - Re: Inter Thread Coomunication

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4B16A1B1.9010101@s5r6.in-berlin.de>
Date:	Wed, 02 Dec 2009 18:19:45 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Mai Daftedar <mai.daftedar@...il.com>
CC:	linux-kernel@...r.kernel.org, clemens@...isch.de
Subject: Re: Inter Thread Coomunication

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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/