04-24-2007
Question on creation of Thread pool
dear sir/madam
presently i am in a process of creating a multithread pool using
clone() system call in unix with c programming.
i am facing some problem ie., i am able create multithread pool and
able to keep all the threads in wait state,but when i call kill
(afunction revoke a thread after stopping it through raise
function) all the threads in the pool are revoking instead of only
one.In order to make only single thread to invoke and keep the
rest in wait condition i need to set a flag in clone system call
but i am unable to find that flag.I tried it with all flags that i
got in man and internet but i could not get it.so can anyone send
me the code for the same?
Thanks
Radha
9 More Discussions You Might Find Interesting
1. Solaris
Hi all!
Is there a function in c++ to create new threads.I have writen a class "Thread"
in which I will be calling this thread function to creat threads.
Also is there a function to synchronize threads .I know that we can create objects like semaphores and critical sections to synchronize in... (2 Replies)
Discussion started by: vijlak
2 Replies
2. Solaris
I'm trying to figure out how to simply create a 500Gb ufs file system named
/rec using DiskSuite 4.2.1 on a Solaris 8 platform via command line using two
250Gb partitions on two different disks. Does anyone know what the proper
command string and options are to perform this task? Would I use the... (2 Replies)
Discussion started by: ruger14
2 Replies
3. Infrastructure Monitoring
Here are the details.
cnjr-opennms>root$ zfs list
NAME USED AVAIL REFER MOUNTPOINT
openpool 20.6G 46.3G 35.5K /openpool
openpool/ROOT 15.4G 46.3G 18K legacy
openpool/ROOT/rds 15.4G 46.3G 15.3G /
openpool/ROOT/rds/var 102M ... (3 Replies)
Discussion started by: pupp
3 Replies
4. Shell Programming and Scripting
#include <stdio.h>
#include <stdlib.h>
#include <pthread.h>
void *fork_thread(void *ptr );
main()
{
pthread_t thread1;
char *message1 = "Thread 1";
int iret1;
iret1 = pthread_create( &thread1, NULL, fork_thread, (void*) message1);
exit(0);
}
Void *fork_thread(... (3 Replies)
Discussion started by: annapurna konga
3 Replies
5. Shell Programming and Scripting
Void *fork_thread( void *ptr )
i am getting error in this line
please help me out (1 Reply)
Discussion started by: annapurna konga
1 Replies
6. Solaris
I created a pool the other day. I created a 10 gig files just for a test, then deleted it.
I proceeded to create a few files systems. But for some reason the pool shows 10% full, but the files systems are both at 1%? Both files systems share the same pool.
When I ls -al the pool I just... (6 Replies)
Discussion started by: mrlayance
6 Replies
7. Solaris
i have server carry more than 50 zone
i want to create 2 resource pool
assign 40 zone to resource pool number 1
assign 10 zone to resource pool number 2
how can i do that (1 Reply)
Discussion started by: coxmanchester
1 Replies
8. UNIX for Dummies Questions & Answers
hello everyone. I want to implement a thread pool, with 10 threads most. Inside main,I call a function (lets say it foo) wich creates (if it is needed) or uses an existing thread from the pool and sends it to do a job.My problem is that I dont know how to pass the argument from the main to the... (2 Replies)
Discussion started by: garag11
2 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I have below code for disk creation
disk_list=$(ls /dev/sd)
for disk in $disk_list
do
pvcreate $i
done
So what my understanding is first it is checking the disk under /dev sdb,sdc,sdd,...sdz whether 25 disk are existing
if not then its creating the 25 physical volume.
I... (4 Replies)
Discussion started by: stew
4 Replies
LEARN ABOUT CENTOS
libtalloc_pools
libtalloc_pools(3) talloc libtalloc_pools(3)
NAME
libtalloc_pools - Chapter 5: Memory pools
Memory pools
Allocation of a new memory is an expensive operation and large programs can contain thousands of calls of malloc() for a single
computation, where every call allocates only a very small amount of the memory. This can result in an undesirable slowdown of the
application. We can avoid this slowdown by decreasing the number of malloc() calls by using a memory pool.
A memory pool is a preallocated memory space with a fixed size. If we need to allocate new data we will take the desired amount of the
memory from the pool instead of requesting a new memory from the system. This is done by creating a pointer that points inside the
preallocated memory. Such a pool must not be reallocated as it would change its location - pointers that were pointing inside the pool
would become invalid. Therefore, a memory pool requires a very good estimate of the required memory space.
The talloc library contains its own implementation of a memory pool. It is highly transparent for the programmer. The only thing that needs
to be done is an initialization of a new pool context using talloc_pool() - which can be used in the same way as any other context.
Refactoring of existing code (that uses talloc) to take the advantage of a memory pool is quite simple due to the following properties of
the pool context:
o if we are allocating data on a pool context, it takes the desired amount of memory from the pool,
o if the context is a descendant of the pool context, it takes the space from the pool as well,
o if the pool does not have sufficient portion of memory left, it will create a new non-pool context, leaving the pool intact
/* allocate 1KiB in a pool */
TALLOC_CTX *pool_ctx = talloc_pool(NULL, 1024);
/* Take 512B from the pool, 512B is left there */
void *ptr = talloc_size(pool_ctx, 512);
/* 1024B > 512B, this will create new talloc chunk outside
the pool */
void *ptr2 = talloc_size(ptr, 1024);
/* The pool still contains 512 free bytes
* this will take 200B from them. */
void *ptr3 = talloc_size(ptr, 200);
/* This will destroy context 'ptr3' but the memory
* is not freed, the available space in the pool
* will increase to 512B. */
talloc_free(ptr3);
/* This will free memory taken by 'pool_ctx'
* and 'ptr2' as well. */
talloc_free(pool_ctx);
The above given is very convenient, but there is one big issue to be kept in mind. If the parent of a talloc pool child is changed to a
parent that is outside of this pool, the whole pool memory will not be freed until the child is freed. For this reason we must be very
careful when stealing a descendant of a pool context.
TALLOC_CTX *mem_ctx = talloc_new(NULL);
TALLOC_CTX *pool_ctx = talloc_pool(NULL, 1024);
struct foo *foo = talloc(pool_ctx, struct foo);
/* mem_ctx is not in the pool */
talloc_steal(mem_ctx, foo);
/* pool_ctx is marked as freed but the memory is not
deallocated, accessing the pool_ctx again will cause
an error */
talloc_free(pool_ctx);
/* This deallocates the pool_ctx. */
talloc_free(mem_ctx);
It may often be better to copy the memory we want instead of stealing it to avoid this problem. If we do not need to retain the context
name (to keep the type information), we can use talloc_memdup() to do this.
Copying the memory out of the pool may, however, discard all the performance boost given by the pool, depending on the size of the copied
memory. Therefore, the code should be well profiled before taking this path. In general, the golden rule is: if we need to steal from the
pool context, we should not use a pool context.
Version 2.0 Tue Jun 17 2014 libtalloc_pools(3)