Child threads communicating with main thread via pipes Post: 302666911

10 More Discussions You Might Find Interesting

1. Programming

Implementing 2 pipes between a parent and child process

Hi all, I'm trying to write a program that has some data it wants to send through a filter program(in this case tr), and then recieve the output from that filter program. The way I'm trying to do it is by setting up two pipes between the programs and piping the data in through one pipe and back...

2. Programming

Can SIGTERM to main process kill the detached threads?

Hi, I am stuck up with a strange problem. I am writing an application - a kinda tracker that reads data from memcache and invokes theads to process each record of the memcache. I dont want to join all my threads because my tracker should poll the cache in regular intervals say sum 300...

3. Shell Programming and Scripting

starting many child threads simultaneously

i have a parent process and 5 child process. As soon as the parent process is completed the 5 child processes need to start simultaneously (like multithreading) All I need to do in a shell script the child process is a function can any one help me on this thanks in advance

4. Programming

IPC - pipes between parent and child process

Hi guys, I'm having some problem here, I'm studying pipes, and i want to create a shell in C and at this point a don't want to use semaphores, instead I want to use tricks. Straight to the doubt: I've a parent and a child process, and both of them has some code to execute, and the child process...

5. Programming

Parent Thread Of Child Thread

Parent Thread Of Child Thread Suppose a process creates some threads say threadC and threadD. Later on each of these threads create new child threads say threadC1, threadC2, threadC3 etc. So a tree of threads will get created. Is there any way to find out the parent thread of one such...

6. Programming

creating multiple threads using single thread id

Hi all, Can I create multiple threads using single thread_id like pthread_t thread_id; pthread_create(&thread_id, NULL, &print_xs, NULL); pthread_create(&thread_id, NULL, &print_ys, NULL); pthread_create(&thread_id, NULL, &print_zs, NULL); pthread_join(thread_id, NULL); what...

7. Programming

unnamed pipes and threads

Hi! I am writing a C program that will create a child, child will create a thread and the thread will send a message to a unnamed pipe and will print the message before exiting. here is my work: #include <sys/types.h> #include <unistd.h> #include <stdio.h> #include <stdlib.h> #include...

8. Programming

Killing a Child Thread

What is the best way for a parent to kill a child thread that has blocked on a command it cannot finish and will never read another line of its code? Will pthread_cancel() work with a thread that will never stop processing its current line of code? Thanks.

9. IP Networking

Message passing from child to parent using pipes

Hi, I am trying my hand in networking programming in C, and got stuck in piping. I was following some tutorial and did the forking like : while (1) { newsockfd = accept(sockfd, (struct sockaddr *) &cli_addr, &clilen); if (newsockfd < 0) ...

10. UNIX for Advanced & Expert Users

How to kill a thread among several threads belongs to a process?

I would like to know is there any we can kill a single thread among multiple threads belongs to process? Since Signal action is process wise not per thread, i strongly feel that we can not or for that mater from external sources as well single thread can not be killed which is critical section...

LEARN ABOUT OSF1

nfsiod

nfsiod(8)						      System Manager's Manual							 nfsiod(8)

NAME

       nfsiod, biod - The local NFS compatible asynchronous I/O daemon

SYNOPSIS

       nfsiod [ numthreads ]

DESCRIPTION

       The  nfsiod  daemon  runs  on  an  NFS  compatible client machine and spawns several IO threads to service asynchronous I/O requests to its
       server.	The I/O threads improve performance of both NFS reads and writes. Both try to enlist the aid of an idle I/O thread.   If  none	is
       available, the process itself issues the request to the server and waits for the reply.

       The  optimum number of I/O threads to run depends on many variables, such as how quickly the client will be writing, how many files will be
       accessed simultaneously, and the behaviour of the NFS server. For use with a Tru64 UNIX server, 7 is a good number of I/O threads for  most
       systems.

       When  reading,  if  the client believes the process is reading a file sequentially, it requests an I/O thread to read a block ahead of what
       the process is currently requesting.  If the readahead completes before the process asks for that block, then the  subsequent  read  system
       call  for that data completes immediately and does not have to wait for the NFS request to complete.  Read ahead will be triggered again so
       the read may find that next block available as well.

       When writing a file, the client takes the process's data, passes the request to an I/O thread and immediately returns to the  process.	If
       the  process is writing data faster than the network or server can process, then eventually all the I/O threads become busy and the process
       has to handle a NFS write itself.  This means the process has to wait until the server finishes the write.  For Tru64 UNIX servers, the NFS
       block  size  is	8Kb and UFS tries to cluster I/O 64Kbs at a time.  If the client is running with 7 I/O threads, 8 write requests can be in
       progress at once.  This allows the client and server to write data 64Kbs at a time and is the reason for recommending 7 I/O threads.

       Unlike nfsd, each client thread can use either UDP or TCP.  However, if TCP mounts are active, the nfsiod process will time out, close idle
       TCP connections, and acknowledge any connections closed by the server.

       The nfsiod process is also responsible for syncing the access time and modify times for special files and named pipes (fifos).  Because I/O
       to these files does not go through the NFS server, NFS clients have to directly update the access time and modify time attributes.

       The client threads are implemented as kernel threads; they are part of Process ID 0, not the nfsiod process.  The ps axml command  displays
       idle  I/O  threads  under  PID  0.  Idle threads will be waiting on nfsiod_wait.  Therefore, if 7 I/O threads are configured, only 1 nfsiod
       process is displayed in the output from the ps command, although 7 client threads are available to handle NFS requests.

FILES

       Specifies the command path Specifies the file for logging NFS activity.

RELATED INFORMATION

       Commands: nfsd(8), nfsstat(8)

       Daemons: async_daemon(2) delim off

																	 nfsiod(8)

10 More Discussions You Might Find Interesting

1. Programming

Implementing 2 pipes between a parent and child process

Discussion started by: bwgoudey

2. Programming

Can SIGTERM to main process kill the detached threads?

Discussion started by: deepti_v25

3. Shell Programming and Scripting

starting many child threads simultaneously

Discussion started by: trichyselva

4. Programming

IPC - pipes between parent and child process

Discussion started by: pharaoh