08-05-2002
There should be no difference at all between piping between two threads or two processes.
The important thing about pipes, no matter how they're connected, is to use each as a one-way-conduit, despite its ability to be two-way. That way you avoid synchronization problems. In your question, it sounds like the direction of data flow is one directional, which means that one pipe should do the trick.
What is it about threads that is making you think there is anything unusual going on? Can you maybe phrase your question more specifically?
10 More Discussions You Might Find Interesting
1. Programming
hi all!
I wanted to know how to synchronize multiple threads in unix
It would be better if someone give some code samples
Thanx (1 Reply)
Discussion started by: bankpro
1 Replies
2. IP Networking
Hi All,
Please explain me when i have to use multiple process and when I have to use Multiple threads? Please give me an example.It will be very helpful for me.
Thanks in advance. (0 Replies)
Discussion started by: ashleykumar
0 Replies
3. UNIX for Dummies Questions & Answers
Hi. I just found this site while searching for some info on a problem and thought I'd see if anyone else knows the answer.
I have two threads that are connected by a pipe. Thread A can write to the pipe and Thread B can read the data from the pipe. My problem is that when I use select() in... (3 Replies)
Discussion started by: willil
3 Replies
4. Shell Programming and Scripting
Hi,
I need to spawn mutilpe threads , each invoking a different set of shell scripts, in parallel.
What would be the best way to do that.
Any sample script would greatly help. I am a novice at Unix so any help is much appreciated.
Thanks (5 Replies)
Discussion started by: neeto
5 Replies
5. UNIX for Advanced & Expert Users
Hi Friends,
I am designing a solution for a problem: in which my master thread receiving network message and processing them, during processing of each message i need to communicate remote database (that is actually a separate external module)that cause a delay of arount 2 second (), After... (1 Reply)
Discussion started by: johnray31
1 Replies
6. Programming
Hi,
Can anyone give me any idea when multiple processes access a file (like opening it, modifying it etc.) how can the synchronization can be done if they can access the same file at any time? How can this scenario is different from when multiple threads access a same file, modifying it etc- in... (7 Replies)
Discussion started by: sanzee
7 Replies
7. UNIX for Dummies Questions & Answers
Hello all,
I have a directory of files of varying sizes.
I want to copy all these files in n number of threads to another directory such that each
copy set is more or less the same size.
Example :
Say /mydirA
It has around say 23 files of various sizes.
Number of copy... (0 Replies)
Discussion started by: samoo
0 Replies
8. Shell Programming and Scripting
Hi,
I have a list of URLs in a csv file which I'm checking for page status. It just prints the URL and the status as output. This works perfectly fine.
I'm looking to run this in multiple threads to make this process faster.
I'm pretty new to Perl and I managed to complete this. It would be... (9 Replies)
Discussion started by: kzenthil
9 Replies
9. Shell Programming and Scripting
Hello,
In a unix Solaris environment, (for simulation) how to start multiple threads (as Light Weight Process, not background process)?
thanks,
J. (7 Replies)
Discussion started by: seafan
7 Replies
10. Shell Programming and Scripting
Hi , i need to run multiple scripts parallely ,on my server....i have 8 cpus . planning to run minimum of 6 scripts paralley ....could you please suggest someone .
thanks in advance , (3 Replies)
Discussion started by: Huvan
3 Replies
LEARN ABOUT DEBIAN
multithreading_support
multithreading_support(3) Coin multithreading_support(3)
NAME
multithreading_support - Multithreading Support in Coin The support in Coin for using multiple threads in application programs and the Coin
library itself, consists of two main features:
o Coin provides platform-independent thread-handling abstraction classes. These are classes that the application programmer can freely use
in her application code to start new threads, control their execution, work with mutexes and do other tasks related to handling multiple
threads.
The classes in question are SbThread, SbMutex, SbStorage, SbBarrier, SbCondVar, SbFifo, SbThreadAutoLock, SbRWMutex, and SbTypedStorage.
See their respective documentation for the detailed information.
The classes fully hides the system-specific implementation, which is either done on top of native Win32 (if on Microsoft Windows), or over
POSIX threads (on UNIX and UNIX-like systems).
o The other aspect of our multi-threading support is that Coin can be specially configured so that rendering traversals of the scene graph
are done in a thread-safe manner. This means e.g. that it is possible to have Coin render the scene in parallel on multiple CPUs for
multiple rendering pipes, to better take advantage of such high-end systems (like CAVE environments, for instance).
Thread-safe render traversals are off by default, because there is a small overhead involved which would make rendering (very) slightly
slower on single-threaded invocations.
To get a Coin library built with thread-safe rendering, one must actively re-configure Coin and build a special, local version. For
configure-based builds (UNIX and UNIX-like systems, or with Cygwin on Microsoft Windows) this is done with the option '--enable-threadsafe'
to Autoconf configure. For how to change the configuration and re-build with Visual Studio, get in touch with us at 'coin-
support@coin3d.org'.
There are some restrictions and other issues which it is important to be aware of:
o We do not yet provide any support for binding the multi-threaded rendering support into the SoQt / SoWin / etc GUI bindings, and neither
do we provide bindings against any specific library that handles multi-pipe rendering. This means the application programmer will have to
possess some expertise, and put in some effort, to be able to utilize multi-pipe rendering with Coin.
o Rendering traversals is currently the only operation which we publicly support to be thread-safe. There are other aspects of Coin that we
know are thread-safe, like most other action traversals beside just rendering, but we make no guarantees in this regard.
o Be careful about using a separate thread for changing Coin structures versus what is used for the application's GUI event thread.
We are aware of at least issues with Qt (and thereby SoQt), where you should not modify the scene graph in any way in a thread separate
from the main Qt thread. This because it will trigger operations where Qt is not thread-safe.
Since:
Coin 2.0
Version 3.1.3 Wed May 23 2012 multithreading_support(3)